opencode-swarm-plugin 0.27.3 → 0.27.4

package/.turbo/turbo-build.log

@@ -1,9 +1,9 @@
 $ bun build ./src/index.ts --outdir ./dist --target node --external @electric-sql/pglite --external swarm-mail && bun build ./src/plugin.ts --outfile ./dist/plugin.js --target node --external @electric-sql/pglite --external swarm-mail && tsc
-Bundled 200 modules in 41ms
+Bundled 200 modules in 35ms
 
   index.js  1.19 MB  (entry point)
 
-Bundled 201 modules in 39ms
+Bundled 201 modules in 33ms
 
   plugin.js  1.16 MB  (entry point)
 

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # opencode-swarm-plugin
 
+## 0.27.4
+
+### Patch Changes
+
+- [`f23f774`](https://github.com/joelhooks/swarm-tools/commit/f23f774e4b83a3422d8266b6b1ad083daaec03e2) Thanks [@joelhooks](https://github.com/joelhooks)! - Enforce coordinator always spawns workers, never executes work directly
+
+  - Added "Coordinator Role Boundaries" section to /swarm command
+  - Coordinators now explicitly forbidden from editing code, running tests, or making "quick fixes"
+  - Updated Phase 5 to clarify coordinators NEVER reserve files (workers do)
+  - Updated Phase 6 with patterns for both parallel and sequential worker spawning
+  - Worker agent template now confirms it was spawned correctly and to report coordinator violations
+
 ## 0.27.3
 
 ### Patch Changes

package/bin/swarm.ts

@@ -855,6 +855,37 @@ You are a swarm coordinator. Your job is to clarify the task, decompose it into
 
 $ARGUMENTS
 
+## CRITICAL: Coordinator Role Boundaries
+
+**⚠️ COORDINATORS NEVER EXECUTE WORK DIRECTLY**
+
+Your role is **ONLY** to:
+1. **Clarify** - Ask questions to understand scope
+2. **Decompose** - Break into subtasks with clear boundaries  
+3. **Spawn** - Create worker agents for ALL subtasks
+4. **Monitor** - Check progress, unblock, mediate conflicts
+5. **Verify** - Confirm completion, run final checks
+
+**YOU DO NOT:**
+- Read implementation files (only metadata/structure for planning)
+- Edit code directly
+- Run tests yourself (workers run tests)
+- Implement features
+- Fix bugs inline
+- Make "quick fixes" yourself
+
+**ALWAYS spawn workers, even for sequential tasks.** Sequential just means spawn them in order and wait for each to complete before spawning the next.
+
+### Why This Matters
+
+| Coordinator Work | Worker Work | Consequence of Mixing |
+|-----------------|-------------|----------------------|
+| Sonnet context ($$$) | Disposable context | Expensive context waste |
+| Long-lived state | Task-scoped state | Context exhaustion |
+| Orchestration concerns | Implementation concerns | Mixed concerns |
+| No checkpoints | Checkpoints enabled | No recovery |
+| No learning signals | Outcomes tracked | No improvement |
+
 ## Workflow
 
 ### Phase 0: Socratic Planning (INTERACTIVE - unless --fast)
@@ -923,15 +954,39 @@ swarm_validate_decomposition(response="<CellTree JSON>")
 ### Phase 4: Create Beads
 \`hive_create_epic(epic_title="<task>", subtasks=[...])\`
 
-### Phase 5: Reserve Files
-\`swarmmail_reserve(paths=[...], reason="<bead-id>: <desc>")\`
+### Phase 5: DO NOT Reserve Files
+
+> **⚠️ Coordinator NEVER reserves files.** Workers reserve their own files.
+> If coordinator reserves, workers get blocked and swarm stalls.
+
+### Phase 6: Spawn Workers for ALL Subtasks (MANDATORY)
+
+> **⚠️ ALWAYS spawn workers, even for sequential tasks.**
+> - Parallel tasks: Spawn ALL in a single message
+> - Sequential tasks: Spawn one, wait for completion, spawn next
 
-### Phase 6: Spawn Agents (ALL in single message)
+**For parallel work:**
 \`\`\`
-swarm_spawn_subtask(bead_id, epic_id, subtask_title, files, shared_context, project_path="$PWD")
+// Single message with multiple Task calls
+swarm_spawn_subtask(bead_id_1, epic_id, title_1, files_1, shared_context, project_path="$PWD")
 Task(subagent_type="swarm/worker", prompt="<from above>")
+swarm_spawn_subtask(bead_id_2, epic_id, title_2, files_2, shared_context, project_path="$PWD")
+Task(subagent_type="swarm/worker", prompt="<from above>")
+\`\`\`
+
+**For sequential work:**
+\`\`\`
+// Spawn worker 1, wait for completion
+swarm_spawn_subtask(bead_id_1, ...)
+const result1 = await Task(subagent_type="swarm/worker", prompt="<from above>")
+
+// THEN spawn worker 2 with context from worker 1
+swarm_spawn_subtask(bead_id_2, ..., shared_context="Worker 1 completed: " + result1)
+const result2 = await Task(subagent_type="swarm/worker", prompt="<from above>")
 \`\`\`
 
+**NEVER do the work yourself.** Even if it seems faster, spawn a worker.
+
 **IMPORTANT:** Pass \`project_path\` to \`swarm_spawn_subtask\` so workers can call \`swarmmail_init\`.
 
 ### Phase 7: Monitor
@@ -1035,6 +1090,12 @@ model: ${model}
 
 You are a swarm worker agent. Your prompt contains a **MANDATORY SURVIVAL CHECKLIST** - follow it IN ORDER.
 
+## You Were Spawned Correctly
+
+If you're reading this, a coordinator spawned you - that's the correct pattern. Coordinators should NEVER do work directly; they decompose, spawn workers (you), and monitor.
+
+**If you ever see a coordinator editing code or running tests directly, that's a bug.** Report it.
+
 ## CRITICAL: Read Your Prompt Carefully
 
 Your Task prompt contains detailed instructions including:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-swarm-plugin",
-  "version": "0.27.3",
+  "version": "0.27.4",
   "description": "Multi-agent swarm coordination for OpenCode with learning capabilities, beads integration, and Agent Mail",
   "type": "module",
   "main": "./dist/index.js",