opencodekit 0.16.5 → 0.16.7

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

@@ -1,12 +1,37 @@
 # Beads PRD Template
 
-**Bead:** bd-[id]
-**Created:** [date]
-**Status:** Draft
+**Bead:** bd-[id]  
+**Created:** [date]  
+**Status:** Draft | In Review | Approved
 
-## Goal
+## Bead Metadata
 
-What exactly are we building and why does it exist?
+```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 waiting on this one
+estimated_hours: 2 # Time estimate for planning
+```
+
+---
+
+## Problem Statement
+
+### What problem are we solving?
+
+[Clear description of the problem. Include user impact and business impact.]
+
+### Why now?
+
+[What triggered this work? Cost of inaction?]
+
+### Who is affected?
+
+- **Primary users:** [Description]
+- **Secondary users:** [Description]
+
+---
 
 ## Scope
 
@@ -17,20 +42,55 @@ What exactly are we building and why does it exist?
 ### Out-of-Scope
 
 - [List what's explicitly off-limits]
+- [Deferred to future iterations]
+
+---
+
+## Proposed Solution
+
+### Overview
+
+[One paragraph describing what this feature does when complete.]
 
-## User Flow (if user-facing)
+### User Flow (if user-facing)
 
 1. [Step 1]
 2. [Step 2]
 3. [Step 3]
 
+---
+
+## Requirements
+
+### Functional 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]
+
+### Non-Functional Requirements
+
+- **Performance:** [constraint if applicable]
+- **Security:** [constraint if applicable]
+- **Accessibility:** [WCAG level if applicable]
+- **Compatibility:** [constraint if applicable]
+
+---
+
 ## Success Criteria
 
-- [ ] [Specific, measurable criteria 1]
+- [ ] [Specific, measurable criterion 1]
   - Verify: `[command or manual check]`
-- [ ] [Specific, measurable criteria 2]
+- [ ] [Specific, measurable criterion 2]
   - Verify: `[command or manual check]`
 
+---
+
 ## Technical Context
 
 ### Existing Patterns
@@ -41,26 +101,44 @@ What exactly are we building and why does it exist?
 
 - `src/relevant/file.ts` - Why relevant
 
-## Risks
+### Affected Files
 
-- [Risk 1 + mitigation]
+Files this bead will modify (for conflict detection):
 
-## Notes
+```yaml
+files:
+  - src/path/to/file.ts # Why
+  - src/path/to/other.ts # Why
+```
 
-[Additional context or constraints]
+---
+
+## Risks & Mitigations
+
+| Risk   | Likelihood   | Impact       | Mitigation      |
+| ------ | ------------ | ------------ | --------------- |
+| Risk 1 | High/Med/Low | High/Med/Low | How to mitigate |
+
+---
+
+## Open Questions
+
+| Question   | Owner | Due Date | Status        |
+| ---------- | ----- | -------- | ------------- |
+| Question 1 | Name  | Date     | Open/Resolved |
 
 ---
 
 ## Tasks
 
-Write tasks in a machine-convertible format for `prd-task`.
+Write tasks in a machine-convertible format for `prd-task` skill.
 
-Rules:
+**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.
+- Each task is a `### <Title> [category]` heading
+- Provide one sentence describing the end state
+- Include `**Metadata:**` with dependency info
+- Include `**Verification:**` with bullet steps proving it works
 
 ### <Task Title> [category]
 
@@ -106,3 +184,9 @@ files: []
 | `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"]` |
+
+---
+
+## Notes
+
+[Additional context, constraints, or decisions]

package/dist/template/.opencode/memory/project/gotchas.md

@@ -0,0 +1,31 @@
+---
+purpose: Footguns, edge cases, and warnings discovered during development
+updated: 2026-02-04
+---
+
+# Gotchas
+
+Track unexpected behaviors, edge cases, and warnings here. Update when you hit something surprising.
+
+## OpenCode Config
+
+- **`compaction` key invalid**: Not in official schema at opencode.ai/config.json. Remove if present.
+- **`experimental` key invalid**: Not in schema. Remove if present.
+- **`tools` key invalid**: Not in schema. Remove if present.
+- **`formatter` valid but undocumented**: Works but missing from schema (schema incomplete).
+
+## Memory System
+
+- Subagents (explore, scout, review) should NOT write to memory - only leader agents
+- Use `observation: false` and `memory-update: false` in agent configs to enforce
+
+## Build System
+
+- `dist/` is generated - never edit directly
+- Build copies `.opencode/` to `dist/template/` via rsync
+- Run `npm run build` to regenerate
+
+## Beads
+
+- Only leader agents (build, plan) should modify beads state
+- Subagents read with `br show <id>`, report findings back

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

@@ -45,7 +45,7 @@ This file is automatically injected into ALL AI prompts via `opencode.json` inst
 ## Active Integrations
 
 - **OpenCode AI:** @opencode-ai/plugin (^1.1.12) - OpenCode integration
-- **Beads CLI:** @beads/bd (^0.29.0) - Task tracking CLI
+- **Beads CLI:** beads_rust (br) - Task tracking CLI
 
 ---
 

package/dist/template/.opencode/opencode.json

@@ -43,11 +43,6 @@
 		}
 	},
 	"autoupdate": false,
-	"compaction": {
-		"auto": true,
-		"prune": true
-	},
-	"experimental": {},
 	"formatter": {
 		"biome": {
 			"command": ["npx", "@biomejs/biome", "check", "--write", "$FILE"],
@@ -170,18 +165,12 @@
 					"reasoning": true,
 					"tool_call": true,
 					"options": {
-						"reasoningEffort": "medium"
-					},
-					"variants": {
-						"high": {
-							"options": {
-								"reasoningEffort": "high"
-							}
+						"thinking": {
+							"type": "enabled",
+							"budgetTokens": 31999
 						},
-						"max": {
-							"options": {
-								"reasoningEffort": "max"
-							}
+						"interleaved": {
+							"field": "reasoning_content"
 						}
 					}
 				}
@@ -262,7 +251,8 @@
 					"tool_call": true,
 					"options": {
 						"reasoningEffort": "medium",
-						"reasoningSummary": "auto"
+						"reasoningSummary": "auto",
+						"textVerbosity": "medium"
 					},
 					"variants": {
 						"high": {
@@ -287,7 +277,8 @@
 					"tool_call": true,
 					"options": {
 						"reasoningEffort": "medium",
-						"reasoningSummary": "auto"
+						"reasoningSummary": "auto",
+						"textVerbosity": "medium"
 					},
 					"variants": {
 						"fast": {
@@ -794,11 +785,6 @@
 	},
 	"share": "manual",
 	"small_model": "opencode/gpt-5-nano",
-	"tools": {
-		"context7-query-docs": true,
-		"context7-resolve-library-id": true,
-		"grepsearch": true
-	},
 	"tui": {
 		"diff_style": "auto",
 		"scroll_acceleration": {

package/dist/template/.opencode/package.json

@@ -11,7 +11,7 @@
     "type-check": "tsc --noEmit"
   },
   "dependencies": {
-    "@opencode-ai/plugin": "1.1.49"
+    "@opencode-ai/plugin": "1.1.51"
   },
   "devDependencies": {
     "@types/node": "^25.1.0",

package/dist/template/.opencode/skill/beads/SKILL.md

@@ -308,12 +308,12 @@ For parallel execution with multiple subagents, use the **beads-bridge** skill:
 skill({ name: "beads-bridge" });
 ```
 
-**beads-bridge** provides:
+**beads-bridge** provides (via unified `swarm` tool):
 
-- `beads-sync` - Sync Beads tasks to OpenCode todos for subagent visibility
-- `swarm-monitor` - Real-time progress tracking and visualization
-- `swarm-plan` - Task classification and dependency analysis
-- `swarm-delegate` - Create delegation packets for workers
+- `swarm({ operation: "sync" })` - Sync Beads tasks to OpenCode todos for subagent visibility
+- `swarm({ operation: "monitor" })` - Real-time progress tracking and visualization
+- `swarm({ operation: "plan" })` - Task classification and dependency analysis
+- `swarm({ operation: "delegate" })` - Create delegation packets for workers
 
 **When to use beads vs beads-bridge:**
 
@@ -321,24 +321,24 @@ skill({ name: "beads-bridge" });
 | ------------------------------ | -------------------------------- |
 | Single agent, linear work      | `beads` skill only               |
 | Multiple agents in parallel    | `beads-bridge` + `beads`         |
-| Need subagents to see tasks    | `beads-bridge` (beads-sync push) |
-| Track worker progress visually | `beads-bridge` (swarm-monitor)   |
+| Need subagents to see tasks    | `beads-bridge` (swarm sync push) |
+| Track worker progress visually | `beads-bridge` (swarm monitor)   |
 
 **Example swarm workflow:**
 
 ```typescript
 // 1. Push beads to OpenCode todos (subagents can see via todoread)
-beads_sync({ operation: "push" });
+swarm({ operation: "sync", action: "push" });
 
 // 2. Spawn workers in parallel using Task tool
 Task({ subagent_type: "general", description: "Worker 1", prompt: "..." });
 Task({ subagent_type: "general", description: "Worker 2", prompt: "..." });
 
 // 3. Monitor progress
-swarm_monitor({ operation: "render_block", team_name: "my-swarm" });
+swarm({ operation: "monitor", action: "render_block", team_name: "my-swarm" });
 
 // 4. Pull completed work back to beads
-beads_sync({ operation: "pull" });
+swarm({ operation: "sync", action: "pull" });
 ```
 
 ## Rules

package/dist/template/.opencode/skill/beads-bridge/SKILL.md

@@ -24,13 +24,17 @@ Bridge between Beads git-backed task tracking, OpenCode's native todo system, an
 
 **Key Tools**:
 
-| Tool             | Purpose                                 | When to Use                              |
-| ---------------- | --------------------------------------- | ---------------------------------------- |
-| `beads-sync`     | Sync Beads ↔ OpenCode todos             | Start of session, before spawning swarms |
-| `swarm-monitor`  | Progress tracking (visualization)       | During swarm execution                   |
-| `swarm-plan`     | Task classification + dependency graphs | Before spawning workers                  |
-| `swarm-delegate` | Create delegation packets               | Assigning work to workers                |
-| `Task`           | Parallel subagent execution             | Spawning worker swarms                   |
+| Tool    | Purpose                     | When to Use                                          |
+| ------- | --------------------------- | ---------------------------------------------------- |
+| `swarm` | Unified swarm coordination  | All swarm operations (sync, monitor, plan, delegate) |
+| `Task`  | Parallel subagent execution | Spawning worker swarms                               |
+
+**swarm operations:**
+
+- `sync`: Sync Beads ↔ OpenCode todos (start of session, before spawning)
+- `monitor`: Progress tracking/visualization (during swarm execution)
+- `plan`: Task classification + dependency graphs (before spawning workers)
+- `delegate`: Create delegation packets (assigning work to workers)
 
 ## When to Use This Skill
 
@@ -48,8 +52,9 @@ Make Beads tasks visible to subagents:
 
 ```typescript
 // Push Beads to OpenCode todos
-const result = await beads_sync({
-  operation: "push",
+const result = await swarm({
+  operation: "sync",
+  action: "push",
   filter: "open", // or "in_progress", "all"
 });
 
@@ -63,8 +68,9 @@ Check current swarm progress:
 
 ```typescript
 // Check swarm status
-const status = await swarm_monitor({
-  operation: "status",
+const status = await swarm({
+  operation: "monitor",
+  action: "status",
   team_name: "api-refactor-swarm",
 });
 
@@ -72,8 +78,9 @@ const stats = JSON.parse(status).summary;
 console.log(`Workers: ${stats.total_workers}, Completed: ${stats.completed}`);
 
 // Render TUI for visualization
-const ui = await swarm_monitor({
-  operation: "render_block",
+const ui = await swarm({
+  operation: "monitor",
+  action: "render_block",
   team_name: "api-refactor-swarm",
 });
 console.log(ui);
@@ -85,8 +92,9 @@ For work that spans multiple sessions, use shared task lists:
 
 ```typescript
 // Create a shared list that persists across sessions
-const list = await beads_sync({
-  operation: "create_shared",
+const list = await swarm({
+  operation: "sync",
+  action: "create_shared",
   name: "api-refactor-swarm",
   tasks: JSON.stringify([
     { id: "task-1", content: "Refactor auth endpoint", status: "pending", priority: "high" },
@@ -95,8 +103,9 @@ const list = await beads_sync({
 });
 
 // Workers update the shared list as they complete work
-await beads_sync({
-  operation: "update_shared",
+await swarm({
+  operation: "sync",
+  action: "update_shared",
   list_id: list.list_id,
   tasks: JSON.stringify([{ id: "task-1", status: "completed" }]),
 });
@@ -108,8 +117,9 @@ Create persistent task lists that survive session boundaries:
 
 ```typescript
 // Create a shared list for a swarm
-const list = await beads_sync({
-  operation: "create_shared",
+const list = await swarm({
+  operation: "sync",
+  action: "create_shared",
   name: "api-refactor-swarm",
   tasks: JSON.stringify([
     { id: "task-1", content: "Refactor auth endpoint", status: "pending", priority: "high" },
@@ -120,7 +130,7 @@ const list = await beads_sync({
 
 // Share the list ID with workers
 console.log(`List ID: ${list.list_id}`);
-// Workers can access via: beads_sync({ operation: "get_shared", list_id: "..." })
+// Workers can access via: swarm({ operation: "sync", action: "get_shared", list_id: "..." })
 ```
 
 ### 5. Worker Updates to Shared List
@@ -129,8 +139,9 @@ Workers can update their task status:
 
 ```typescript
 // Worker completes a task
-await beads_sync({
-  operation: "update_shared",
+await swarm({
+  operation: "sync",
+  action: "update_shared",
   list_id: "shl_abc123",
   tasks: JSON.stringify([{ id: "task-1", status: "completed" }]),
 });
@@ -144,14 +155,15 @@ Full cycle from Beads task to swarm execution and back:
 
 ```typescript
 // 1. Start: Push Beads to todos
-await beads_sync({ operation: "push" });
+await swarm({ operation: "sync", action: "push" });
 
 // 2. Claim the parent Bead
 await bash("br update parent-task --status in_progress");
 
 // 3. Analyze and spawn swarm
-const analysis = await swarm_plan({
-  operation: "analyze",
+const analysis = await swarm({
+  operation: "plan",
+  action: "analyze",
   task: "Implement API refactor",
   files: "src/api/users.ts,src/api/posts.ts,src/api/auth.ts",
 });
@@ -160,11 +172,12 @@ const analysis = await swarm_plan({
 // ... spawn workers, monitor progress ...
 
 // 5. Complete: Pull completed todos back to Beads
-await beads_sync({ operation: "pull" });
+await swarm({ operation: "sync", action: "pull" });
 
 // 6. Clear swarm state
-await swarm_monitor({
-  operation: "clear",
+await swarm({
+  operation: "monitor",
+  action: "clear",
   team_name: "api-refactor-swarm",
 });
 
@@ -176,12 +189,13 @@ await bash("git add .beads/ && git commit -m 'close parent-task'");
 
 ### Pattern B: Dependency-Aware Task Scheduling
 
-Use swarm-plan's dependency graph for proper ordering:
+Use swarm tool's dependency graph for proper ordering:
 
 ```typescript
 // Get full analysis with dependency graph
-const analysis = await swarm_plan({
-  operation: "analyze",
+const analysis = await swarm({
+  operation: "plan",
+  action: "analyze",
   task: "Refactor authentication system",
   files: "src/auth/service.ts,src/auth/types.ts,src/routes/auth.ts,src/middleware/auth.ts",
 });
@@ -216,8 +230,9 @@ When work needs to continue in a new session:
 
 ```typescript
 // End of session 1: Save state to memory and shared list
-await beads_sync({
-  operation: "update_shared",
+await swarm({
+  operation: "sync",
+  action: "update_shared",
   list_id: "api-refactor-swarm",
   tasks: JSON.stringify([
     { id: "worker-1", content: "Auth service", status: "completed" },
@@ -249,13 +264,15 @@ await bash("br sync --flush-only");
 await bash("git add .beads/ && git commit -m 'session handoff'");
 
 // Start of session 2: Check status and continue
-const status = await swarm_monitor({
-  operation: "status",
+const status = await swarm({
+  operation: "monitor",
+  action: "status",
   team_name: "api-refactor-swarm",
 });
 
-const shared = await beads_sync({
-  operation: "get_shared",
+const shared = await swarm({
+  operation: "sync",
+  action: "get_shared",
   list_id: "api-refactor-swarm",
 });
 
@@ -275,29 +292,29 @@ console.log(`Continuing swarm with ${shared.tasks.length} tasks...`);
 
 ```
 SESSION START:
-  beads-sync({ operation: "push" })  // Make Beads visible to subagents
-  swarm-monitor({ operation: "status", team_name: "..." })  // Check swarm status
+  swarm({ operation: "sync", action: "push" })  // Make Beads visible to subagents
+  swarm({ operation: "monitor", action: "status", team_name: "..." })  // Check swarm status
 
 DURING WORK:
-  swarm-monitor({ operation: "progress_update", ... })  // Track worker progress
-  swarm-monitor({ operation: "render_block", ... })  // TUI visualization
-  beads-sync({ operation: "update_shared", ... })  // Cross-session updates
+  swarm({ operation: "monitor", action: "progress_update", ... })  // Track worker progress
+  swarm({ operation: "monitor", action: "render_block", ... })  // TUI visualization
+  swarm({ operation: "sync", action: "update_shared", ... })  // Cross-session updates
 
 SESSION END:
-  beads-sync({ operation: "pull" })  // Sync completed todos back to Beads
-  swarm-monitor({ operation: "clear", team_name: "..." })  // Cleanup swarm state
+  swarm({ operation: "sync", action: "pull" })  // Sync completed todos back to Beads
+  swarm({ operation: "monitor", action: "clear", team_name: "..." })  // Cleanup swarm state
   br sync --flush-only  // Export Beads changes
   git add .beads/ && git commit -m "..."  // Commit changes to git
 
 RECOVERY:
-  beads-sync({ operation: "get_shared", list_id: "..." })  // Get shared task list
-  swarm-monitor({ operation: "status", team_name: "..." })  // Check swarm status
+  swarm({ operation: "sync", action: "get_shared", list_id: "..." })  // Get shared task list
+  swarm({ operation: "monitor", action: "status", team_name: "..." })  // Check swarm status
 ```
 
 ## Rules
 
 1. **Always push Beads at session start** - Subagents need visibility via todoread
-2. **Use shared lists for long-running swarms** - Cross-session persistence via beads-sync
+2. **Use shared lists for long-running swarms** - Cross-session persistence via swarm sync
 3. **Pull completed todos back to Beads** - Keep tracking system in sync
 4. **Check swarm status before spawning** - Avoid duplicate work
 5. **Clear swarm state when done** - Cleanup after completion

package/dist/template/.opencode/skill/brainstorming/SKILL.md

@@ -11,6 +11,10 @@ Help turn ideas into fully formed designs and specs through natural collaborativ
 
 Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
 
+**Part of:** `development-lifecycle` skill (Phase 1: Ideation)
+
+**Output template:** `.opencode/memory/_templates/design.md`
+
 ## The Process
 
 **Understanding the idea:**
@@ -39,15 +43,25 @@ Start by understanding the current project context, then ask questions one at a
 
 **Documentation:**
 
-- Write the validated design to `.beads/artifacts/<bead-id>/design.md` using template from `.opencode/memory/_templates/design.md`
+- Write the validated design to `.beads/artifacts/<bead-id>/design.md`
+- Use template from `.opencode/memory/_templates/design.md`
 - Use elements-of-style:writing-clearly-and-concisely skill if available
 - Commit the design document to git
 
-**Implementation (if continuing):**
+**Next Phase (if continuing):**
+
+- Ask: "Ready to create the PRD?"
+- Load next skill: `skill({ name: "prd" })`
+- This moves to Phase 2: Specification
+
+**Alternative paths:**
+
+- Use `skill({ name: "using-git-worktrees" })` to create isolated workspace first
+- Use `skill({ name: "writing-plans" })` if skipping formal PRD
+
+**Full lifecycle reference:**
 
-- Ask: "Ready to set up for implementation?"
-- Use skill({ name: "using-git-worktrees" }) to create isolated workspace
-- Use skill({ name: "writing-plans" }) to create detailed implementation plan
+- Use `skill({ name: "development-lifecycle" })` to see all phases
 
 ## Key Principles