opencodekit 0.15.20 → 0.16.0

package/dist/template/.opencode/command/verify.md

@@ -0,0 +1,279 @@
+---
+description: Verify implementation completeness, correctness, and coherence
+argument-hint: "<bead-id> [--quick] [--fix]"
+agent: review
+subtask: true
+---
+
+# Verify: $ARGUMENTS
+
+Three-dimensional verification before claiming work complete. Inspired by OpenSpec's verify workflow.
+
+## Load Skills
+
+```typescript
+skill({ name: "beads" });
+skill({ name: "verification-before-completion" });
+skill({ name: "systematic-debugging" });
+```
+
+## Parse Arguments
+
+| Argument    | Default  | Description                      |
+| ----------- | -------- | -------------------------------- |
+| `<bead-id>` | required | The bead to verify               |
+| `--quick`   | false    | Skip coherence check, gates only |
+| `--fix`     | false    | Auto-fix issues where possible   |
+
+---
+
+## Phase 1: Gather Artifacts
+
+```bash
+bd show $ARGUMENTS
+ls .beads/artifacts/$ARGUMENTS/
+```
+
+Read all artifacts:
+
+```bash
+cat .beads/artifacts/$ARGUMENTS/spec.md 2>/dev/null
+cat .beads/artifacts/$ARGUMENTS/plan.md 2>/dev/null
+cat .beads/artifacts/$ARGUMENTS/research.md 2>/dev/null
+cat .beads/artifacts/$ARGUMENTS/design.md 2>/dev/null
+```
+
+---
+
+## Phase 2: Completeness Check
+
+**Are all required artifacts present?**
+
+| Artifact      | Required | Status |
+| ------------- | -------- | ------ |
+| `spec.md`     | Yes      | [ ]    |
+| `plan.md`     | Yes      | [ ]    |
+| `research.md` | No       | [ ]    |
+| `design.md`   | No       | [ ]    |
+
+**Are all tasks in the spec addressed?**
+
+Extract tasks/criteria from spec.md and verify each is implemented:
+
+```markdown
+## Completeness Report
+
+| Requirement       | Status     | Evidence                |
+| ----------------- | ---------- | ----------------------- |
+| [Req 1 from spec] | ✓ Complete | `src/foo.ts:42`         |
+| [Req 2 from spec] | ✓ Complete | `src/bar.ts:15`         |
+| [Req 3 from spec] | ⚠ Partial  | Missing edge case tests |
+| [Req 4 from spec] | ✗ Missing  | Not implemented         |
+```
+
+**Completeness Score:** X/Y requirements met
+
+---
+
+## Phase 3: Correctness Check
+
+**Do the automated gates pass?**
+
+```bash
+# Detect project type and run gates
+ls package.json Cargo.toml pyproject.toml go.mod 2>/dev/null
+```
+
+**Node/TypeScript:**
+
+```bash
+npm run build 2>&1 | tail -10
+npm test 2>&1 | tail -20
+npm run lint 2>&1 | tail -10
+npm run typecheck 2>&1 | tail -10
+```
+
+**Rust:**
+
+```bash
+cargo build 2>&1 | tail -10
+cargo test 2>&1 | tail -20
+cargo clippy -- -D warnings 2>&1 | tail -10
+```
+
+**Python:**
+
+```bash
+pytest 2>&1 | tail -20
+ruff check . 2>&1 | tail -10
+mypy . 2>&1 | tail -10
+```
+
+**Go:**
+
+```bash
+go build ./... 2>&1 | tail -10
+go test ./... 2>&1 | tail -20
+golangci-lint run 2>&1 | tail -10
+```
+
+```markdown
+## Correctness Report
+
+| Gate      | Status | Details                   |
+| --------- | ------ | ------------------------- |
+| Build     | ✓ Pass |                           |
+| Tests     | ✓ Pass | 42 tests, 0 failures      |
+| Lint      | ⚠ Warn | 2 warnings (non-blocking) |
+| Typecheck | ✓ Pass |                           |
+```
+
+**Correctness Score:** X/Y gates passed
+
+---
+
+## Phase 4: Coherence Check (skip with --quick)
+
+**Do artifacts agree with each other?**
+
+Cross-reference artifacts for contradictions:
+
+| Check                        | Status | Issue                                |
+| ---------------------------- | ------ | ------------------------------------ |
+| spec.md ↔ plan.md            | ✓      | Plan addresses all spec requirements |
+| plan.md ↔ implementation     | ✓      | Code follows plan structure          |
+| research.md ↔ implementation | ⚠      | Didn't use recommended approach      |
+| design.md ↔ implementation   | ✓      | Follows design patterns              |
+
+**Common coherence issues:**
+
+- Plan says X, implementation does Y
+- Research recommended approach A, used approach B (without justification)
+- Spec says must-have, implementation treats as optional
+- Design specifies pattern, implementation uses different pattern
+
+```markdown
+## Coherence Report
+
+Contradictions found: 1
+
+1. **Research vs Implementation**
+   - Research recommended: Use `zod` for validation
+   - Implementation uses: Manual validation
+   - Impact: Medium - works but less maintainable
+   - Action: Document decision or refactor
+```
+
+**Coherence Score:** X/Y checks passed
+
+---
+
+## Phase 5: Verification Summary
+
+```
+Verification: $ARGUMENTS
+━━━━━━━━━━━━━━━━━━━━━━━
+
+Dimension        Score    Status
+───────────────────────────────
+Completeness     4/5      ⚠ PARTIAL
+Correctness      4/4      ✓ PASS
+Coherence        3/4      ⚠ PARTIAL
+
+Overall: ⚠ NEEDS ATTENTION
+
+Issues Found:
+─────────────
+BLOCKING (must fix):
+  • [Req 4] Not implemented
+
+NON-BLOCKING (should fix):
+  • [Req 3] Missing edge case tests
+  • Research recommendation not followed
+
+Recommendations:
+────────────────
+1. Implement [Req 4] before closing
+2. Add tests for edge case X
+3. Document why zod was not used, or refactor to use it
+```
+
+---
+
+## Phase 6: Auto-Fix (if --fix)
+
+For fixable issues, attempt automatic resolution:
+
+```typescript
+// If lint issues are fixable
+if (hasLintWarnings && canAutoFix) {
+  bash({ command: "npm run lint -- --fix" });
+}
+
+// If missing tests detected
+if (missingTests) {
+  console.log("Consider adding tests for: [list uncovered code]");
+}
+```
+
+---
+
+## Phase 7: Update Bead Notes
+
+Record verification results in bead:
+
+```bash
+bd note $ARGUMENTS "Verification: [PASS|PARTIAL|FAIL] - [summary]"
+```
+
+---
+
+## Output
+
+```
+Verification Complete: $ARGUMENTS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Result: ✓ READY TO SHIP | ⚠ NEEDS WORK | ✗ BLOCKED
+
+Completeness: [score] - [status]
+Correctness:  [score] - [status]
+Coherence:    [score] - [status]
+
+[If READY TO SHIP]
+Next: /ship $ARGUMENTS
+
+[If NEEDS WORK]
+Fix these before shipping:
+• [issue 1]
+• [issue 2]
+
+[If BLOCKED]
+Cannot proceed until:
+• [blocker 1]
+```
+
+---
+
+## Examples
+
+```bash
+# Full verification
+/verify bd-feature-auth
+
+# Quick check (gates only)
+/verify bd-feature-auth --quick
+
+# Verify and auto-fix where possible
+/verify bd-feature-auth --fix
+```
+
+---
+
+## Related Commands
+
+| Need              | Command            |
+| ----------------- | ------------------ |
+| Ship after verify | `/ship $ARGUMENTS` |
+| Review code       | `/review-codebase` |
+| Check status      | `/status`          |

package/dist/template/.opencode/memory/_templates/README.md

@@ -1,35 +1,73 @@
 ---
 purpose: Index of available memory templates
-updated: 2026-01-12
+updated: 2026-02-01
 ---
 
 # Memory Templates
 
-Copy these templates to `.opencode/memory/project/` when starting a new project.
+Templates for structured artifacts. Copy to `.beads/artifacts/<bead-id>/` when working on a bead.
 
-## Available Templates
+## Artifact Templates (OpenSpec-aligned)
 
-| Template          | Purpose                                        |
-| ----------------- | ---------------------------------------------- |
-| `architecture.md` | Document project structure, modules, data flow |
-| `conventions.md`  | Code style, naming, patterns, commit rules     |
-| `gotchas.md`      | Known issues, edge cases, troubleshooting      |
-| `commands.md`     | Build, test, lint, deploy commands             |
+These follow the OpenSpec artifact flow: proposal → spec → design → tasks.
+
+| Template      | Purpose                            | When to Use                                   |
+| ------------- | ---------------------------------- | --------------------------------------------- |
+| `proposal.md` | Capture WHY a change is needed     | Starting a new feature or significant change  |
+| `spec.md`     | Define WHAT with WHEN/THEN format  | After proposal, before design                 |
+| `tasks.md`    | Implementation checklist           | After design, before coding                   |
+| `prd.md`      | Combined PRD (proposal+spec+tasks) | Quick features that don't need full breakdown |
+| `design.md`   | Architecture decisions             | Complex features needing design exploration   |
+
+## Context Injection
+
+The file `.opencode/memory/project/tech-stack.md` is auto-injected into all AI prompts via `opencode.json` instructions[].
+
+| File            | Purpose                             |
+| --------------- | ----------------------------------- |
+| `tech-stack.md` | Framework, DB, styling, constraints |
+
+**Additional context is captured organically:**
+
+- AI discovers commands by reading package.json and running them
+- AI captures conventions via `observation` tool as it works
+- AI captures gotchas via `observation` tool when encountering issues
+- Architecture learnings are saved to `.opencode/memory/observations/`
 
 ## Usage
 
+### For Beads Work
+
 ```bash
-# Copy template (replace DATE)
-cp _templates/architecture.md ../project/architecture.md
-sed -i '' "s/{{DATE}}/$(date +%Y-%m-%d)/g" ../project/architecture.md
+# Copy artifact templates to bead folder
+cp .opencode/memory/_templates/proposal.md .beads/artifacts/<bead-id>/
+cp .opencode/memory/_templates/spec.md .beads/artifacts/<bead-id>/
+```
 
-# Or create your own from scratch
-touch ../project/architecture.md
+### For Project Documentation
+
+```bash
+# Fill in tech-stack.md when starting a new project
+# Other project knowledge is captured via observation tool
 ```
 
-## Tips
+## Template Philosophy
+
+**Minimal scaffolds, not rigid forms.**
+
+- Templates are starting points, not constraints
+- Fill in what's relevant, delete what's not
+- WHEN/THEN format in specs enables testable requirements
+- Numbered tasks in `tasks.md` are machine-parseable
+- Let AI learn organically rather than pre-filling empty templates
+
+## OpenSpec Alignment
+
+Our templates are inspired by [OpenSpec](https://github.com/Fission-AI/OpenSpec) patterns:
+
+- **Proposal** → Captures motivation and impact
+- **Spec** → Behavioral requirements with scenarios
+- **Tasks** → Numbered, checkboxed implementation steps
+- **Context injection** → Project info in all prompts
 
-- Fill out templates when you first learn about a project
-- Update as you discover new patterns or issues
-- Use `observation` tool for quick notes during work
-- Use `memory-search` to find relevant context later
+Key difference: We're AI-native (no CLI), so templates are simpler and commands provide the detailed guidance that OpenSpec puts in `schema.yaml` instructions.

package/dist/template/.opencode/memory/_templates/prd.md

@@ -60,11 +60,21 @@ Rules:
 - Each task is a `### <Title> [category]` heading.
 - Provide one sentence describing the end state.
 - Include `**Verification:**` with bullet steps proving it works.
+- Include `**Metadata:**` with dependency and parallelization info.
 
 ### <Task Title> [category]
 
 <One sentence describing the end state>
 
+**Metadata:**
+
+```yaml
+depends_on: [] # Task titles that must complete first
+parallel: true # Can run with other parallel tasks
+conflicts_with: [] # Task titles modifying same files
+files: [] # Files this task will modify
+```
+
 **Verification:**
 
 - [Command or check]
@@ -74,6 +84,25 @@ Rules:
 
 <One sentence describing the end state>
 
+**Metadata:**
+
+```yaml
+depends_on: ["<Previous Task Title>"]
+parallel: false
+files: []
+```
+
 **Verification:**
 
 - [Command or check]
+
+---
+
+## Dependency Legend
+
+| Field            | Purpose                                           | Example                                    |
+| ---------------- | ------------------------------------------------- | ------------------------------------------ |
+| `depends_on`     | Must complete before this task starts             | `["Setup database", "Create schema"]`      |
+| `parallel`       | Can run concurrently with other parallel tasks    | `true` / `false`                           |
+| `conflicts_with` | Cannot run in parallel (same files)               | `["Update config"]`                        |
+| `files`          | Files this task modifies (for conflict detection) | `["src/db/schema.ts", "src/db/client.ts"]` |

package/dist/template/.opencode/memory/_templates/project/tech-stack.md

@@ -0,0 +1,50 @@
+---
+purpose: Tech stack, constraints, and integrations for AI context injection
+updated: 2026-02-01
+---
+
+# Tech Stack
+
+This file is automatically injected into ALL AI prompts via `opencode.json` instructions[].
+
+## Framework & Language
+
+- **Framework:** [e.g., Next.js 15, React 19]
+- **Language:** TypeScript (strict mode)
+- **Runtime:** [e.g., Node.js 22, Bun 1.x]
+
+## Styling & UI
+
+- **CSS:** [e.g., Tailwind CSS v4]
+- **Components:** [e.g., shadcn/ui, Radix Primitives]
+- **Design System:** [e.g., Custom tokens in tailwind.config.ts]
+
+## Data & State
+
+- **Database:** [e.g., PostgreSQL via Supabase]
+- **ORM:** [e.g., Drizzle, Prisma]
+- **State Management:** [e.g., Zustand, React Query]
+- **API Style:** [e.g., REST, tRPC, GraphQL]
+
+## Testing
+
+- **Unit Tests:** [e.g., Vitest]
+- **E2E Tests:** [e.g., Playwright]
+- **Coverage Target:** [e.g., 80%]
+
+## Key Constraints
+
+- [Constraint 1: e.g., Must work offline]
+- [Constraint 2: e.g., WCAG 2.1 AA compliance required]
+- [Constraint 3: e.g., Bundle size < 500KB]
+
+## Active Integrations
+
+- [Service 1: e.g., Stripe for payments]
+- [Service 2: e.g., Resend for email]
+- [Service 3: e.g., Sentry for error tracking]
+
+---
+
+_Update this file when tech stack or constraints change._
+_AI will capture architecture, conventions, and gotchas via the `observation` tool as it works._

package/dist/template/.opencode/memory/_templates/proposal.md

@@ -0,0 +1,38 @@
+# Proposal
+
+**Bead:** [bead-id]
+**Author:** [author]
+**Date:** [YYYY-MM-DD]
+
+## Why
+
+<!-- What problem does this solve? Why now? -->
+
+## What Changes
+
+<!-- High-level description of the proposed changes -->
+
+## Capabilities
+
+### New Capabilities
+
+- `capability-name`: Brief description of what it enables
+
+### Modified Capabilities
+
+- `capability-name`: How existing behavior changes
+
+## Impact
+
+### Users Affected
+
+- [User type or system]
+
+### Migration Required
+
+- [ ] Yes / No
+- If yes: [brief migration notes]
+
+## Open Questions
+
+- [ ] [Question that needs answering before proceeding]

package/dist/template/.opencode/memory/_templates/spec.md

@@ -0,0 +1,66 @@
+# Specification
+
+**Bead:** [bead-id]
+**Proposal:** [link to proposal]
+**Date:** [YYYY-MM-DD]
+
+## Bead Metadata
+
+```yaml
+depends_on: [] # Bead IDs that must complete before this one
+parallel: true # Can run concurrently with other parallel beads
+conflicts_with: [] # Bead IDs that modify same files (cannot parallelize)
+blocks: [] # Bead IDs that are waiting on this one
+estimated_hours: 2 # Time estimate for planning
+```
+
+---
+
+## Requirements
+
+### [Requirement Name]
+
+Brief description of what must be true.
+
+#### Scenarios
+
+**WHEN** [precondition or trigger]
+**THEN** [expected outcome]
+
+**WHEN** [edge case condition]  
+**THEN** [expected behavior]
+
+### [Requirement Name]
+
+Brief description.
+
+#### Scenarios
+
+**WHEN** [condition]
+**THEN** [outcome]
+
+---
+
+## Non-Functional Requirements
+
+- **Performance:** [constraint if applicable]
+- **Security:** [constraint if applicable]
+- **Compatibility:** [constraint if applicable]
+
+---
+
+## Affected Files
+
+List files this bead will modify (for conflict detection with other beads):
+
+```yaml
+files:
+  - src/path/to/file.ts # Why
+  - src/path/to/other.ts # Why
+```
+
+---
+
+## Out of Scope
+
+- [Explicitly excluded capability]