opencode-swarm-plugin 0.4.0 → 0.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,277 @@
1
+ ---
2
+ description: Decompose task into parallel subtasks and coordinate agents
3
+ ---
4
+
5
+ You are a swarm coordinator. Take a complex task, break it into beads, and unleash parallel agents.
6
+
7
+ ## Usage
8
+
9
+ ```
10
+ /swarm <task description or bead-id>
11
+ /swarm --to-main <task> # Skip PR, push directly to main (use sparingly)
12
+ /swarm --no-sync <task> # Skip mid-task context sync (for simple independent tasks)
13
+ ```
14
+
15
+ **Default behavior: Feature branch + PR with context sync.** All swarm work goes to a feature branch, agents share context mid-task, and creates a PR for review.
16
+
17
+ ## Step 1: Initialize Session
18
+
19
+ Use the plugin's agent-mail tools to register:
20
+
21
+ ```
22
+ agentmail_init with project_path=$PWD, task_description="Swarm coordinator: <task>"
23
+ ```
24
+
25
+ This returns your agent name and session state. Remember it.
26
+
27
+ ## Step 2: Create Feature Branch
28
+
29
+ **CRITICAL: Never push directly to main.**
30
+
31
+ ```bash
32
+ # Create branch from bead ID or task name
33
+ git checkout -b swarm/<bead-id> # e.g., swarm/trt-buddy-d7d
34
+ # Or for ad-hoc tasks:
35
+ git checkout -b swarm/<short-description> # e.g., swarm/contextual-checkins
36
+
37
+ git push -u origin HEAD
38
+ ```
39
+
40
+ ## Step 3: Understand the Task
41
+
42
+ If given a bead-id:
43
+
44
+ ```
45
+ beads_query with id=<bead-id>
46
+ ```
47
+
48
+ If given a description, analyze it to understand scope.
49
+
50
+ ## Step 4: Select Strategy & Decompose
51
+
52
+ ### Option A: Use the Planner Agent (Recommended)
53
+
54
+ Spawn the `@swarm-planner` agent to handle decomposition:
55
+
56
+ ```
57
+ Task(
58
+ subagent_type="general",
59
+ description="Plan swarm decomposition",
60
+ prompt="You are @swarm-planner. Decompose this task: <task description>. Use swarm_select_strategy and swarm_plan_prompt to guide your decomposition. Return ONLY valid BeadTree JSON."
61
+ )
62
+ ```
63
+
64
+ ### Option B: Manual Decomposition
65
+
66
+ 1. **Select strategy**:
67
+
68
+ ```
69
+ swarm_select_strategy with task="<task description>"
70
+ ```
71
+
72
+ 2. **Get planning prompt**:
73
+
74
+ ```
75
+ swarm_plan_prompt with task="<task description>", strategy="<selected or auto>"
76
+ ```
77
+
78
+ 3. **Create decomposition** following the prompt guidelines
79
+
80
+ 4. **Validate**:
81
+
82
+ ```
83
+ swarm_validate_decomposition with response="<your BeadTree JSON>"
84
+ ```
85
+
86
+ ### Create Beads
87
+
88
+ Once you have a valid BeadTree:
89
+
90
+ ```
91
+ beads_create_epic with epic_title="<parent task>", subtasks=[{title, description, files, priority}...]
92
+ ```
93
+
94
+ **Decomposition rules:**
95
+
96
+ - Each bead should be completable by one agent
97
+ - Beads should be independent (parallelizable) where possible
98
+ - If there are dependencies, order them in the subtasks array
99
+ - Aim for 3-7 beads per swarm (too few = not parallel, too many = coordination overhead)
100
+
101
+ ## Step 5: Reserve Files
102
+
103
+ For each subtask, reserve the files it will touch:
104
+
105
+ ```
106
+ agentmail_reserve with paths=[<files>], reason="<bead-id>: <brief description>"
107
+ ```
108
+
109
+ **Conflict prevention:**
110
+
111
+ - No two agents should edit the same file
112
+ - If overlap exists, merge beads or sequence them
113
+
114
+ ## Step 6: Spawn the Swarm
115
+
116
+ **CRITICAL: Spawn ALL agents in a SINGLE message with multiple Task calls.**
117
+
118
+ Use the prompt generator for each subtask:
119
+
120
+ ```
121
+ swarm_spawn_subtask with bead_id="<bead-id>", epic_id="<epic-id>", subtask_title="<title>", subtask_description="<description>", files=[<files>], shared_context="Branch: swarm/<id>, sync_enabled: true"
122
+ ```
123
+
124
+ Then spawn agents with the generated prompts:
125
+
126
+ ```
127
+ Task(
128
+ subagent_type="general",
129
+ description="Swarm worker: <bead-title>",
130
+ prompt="<output from swarm_spawn_subtask>"
131
+ )
132
+ ```
133
+
134
+ Spawn ALL agents in parallel in a single response.
135
+
136
+ ## Step 7: Monitor Progress (unless --no-sync)
137
+
138
+ Check swarm status:
139
+
140
+ ```
141
+ swarm_status with epic_id="<parent-bead-id>"
142
+ ```
143
+
144
+ Monitor inbox for progress updates:
145
+
146
+ ```
147
+ agentmail_inbox
148
+ ```
149
+
150
+ **When you receive progress updates:**
151
+
152
+ 1. **Review decisions made** - Are agents making compatible choices?
153
+ 2. **Check for pattern conflicts** - Different approaches to the same problem?
154
+ 3. **Identify shared concerns** - Common blockers or discoveries?
155
+
156
+ **If you spot incompatibilities, broadcast shared context:**
157
+
158
+ ```
159
+ agentmail_send with to=["*"], subject="Coordinator Update", body="<guidance>", thread_id="<epic-id>", importance="high"
160
+ ```
161
+
162
+ ## Step 8: Collect Results
163
+
164
+ When agents complete, they send completion messages. Summarize the thread:
165
+
166
+ ```
167
+ agentmail_summarize_thread with thread_id="<epic-id>"
168
+ ```
169
+
170
+ ## Step 9: Complete Swarm
171
+
172
+ Use the swarm completion tool:
173
+
174
+ ```
175
+ swarm_complete with project_key=$PWD, agent_name=<YOUR_NAME>, bead_id="<epic-id>", summary="<what was accomplished>", files_touched=[<all files>]
176
+ ```
177
+
178
+ This:
179
+
180
+ - Runs UBS bug scan on touched files
181
+ - Releases file reservations
182
+ - Closes the bead
183
+ - Records outcome for learning
184
+
185
+ Then sync beads:
186
+
187
+ ```
188
+ beads_sync
189
+ ```
190
+
191
+ ## Step 10: Create PR
192
+
193
+ ```bash
194
+ gh pr create --title "feat: <epic title>" --body "$(cat <<'EOF'
195
+ ## Summary
196
+ <1-3 bullet points from swarm results>
197
+
198
+ ## Beads Completed
199
+ - <bead-id>: <summary>
200
+ - <bead-id>: <summary>
201
+
202
+ ## Files Changed
203
+ <aggregate list>
204
+
205
+ ## Testing
206
+ - [ ] Type check passes
207
+ - [ ] Tests pass (if applicable)
208
+ EOF
209
+ )"
210
+ ```
211
+
212
+ Report summary:
213
+
214
+ ```markdown
215
+ ## Swarm Complete: <task>
216
+
217
+ ### PR: #<number>
218
+
219
+ ### Agents Spawned: N
220
+
221
+ ### Beads Closed: N
222
+
223
+ ### Work Completed
224
+
225
+ - [bead-id]: [summary]
226
+
227
+ ### Files Changed
228
+
229
+ - [aggregate list]
230
+ ```
231
+
232
+ ## Failure Handling
233
+
234
+ If an agent fails:
235
+
236
+ - Check its messages: `agentmail_inbox`
237
+ - The bead remains in-progress
238
+ - Manually investigate or re-spawn
239
+
240
+ If file conflicts occur:
241
+
242
+ - Agent Mail reservations should prevent this
243
+ - If it happens, one agent needs to wait
244
+
245
+ ## Direct-to-Main Mode (--to-main)
246
+
247
+ Only use when explicitly requested. Skips branch/PR:
248
+
249
+ - Trivial fixes across many files
250
+ - Automated migrations with high confidence
251
+ - User explicitly says "push to main"
252
+
253
+ ## No-Sync Mode (--no-sync)
254
+
255
+ Skip mid-task context sharing when tasks are truly independent:
256
+
257
+ - Simple mechanical changes (find/replace, formatting, lint fixes)
258
+ - Tasks with zero integration points
259
+ - Completely separate feature areas with no shared types
260
+
261
+ In this mode:
262
+
263
+ - Agents skip the mid-task progress message
264
+ - Coordinator skips Step 7 (monitoring)
265
+ - Faster execution, less coordination overhead
266
+
267
+ **Default is sync ON** - prefer sharing context. Use `--no-sync` deliberately.
268
+
269
+ ## Strategy Reference
270
+
271
+ | Strategy | Best For | Auto-Detected Keywords |
272
+ | ----------------- | --------------------------- | ---------------------------------------------- |
273
+ | **file-based** | Refactoring, migrations | refactor, migrate, rename, update all, convert |
274
+ | **feature-based** | New features, functionality | add, implement, build, create, feature, new |
275
+ | **risk-based** | Bug fixes, security | fix, bug, security, critical, urgent, hotfix |
276
+
277
+ Use `swarm_select_strategy` to see which strategy is recommended and why.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-swarm-plugin",
3
- "version": "0.4.0",
3
+ "version": "0.6.0",
4
4
  "description": "Multi-agent swarm coordination for OpenCode with learning capabilities, beads integration, and Agent Mail",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
package/src/index.ts CHANGED
@@ -254,6 +254,12 @@ export {
254
254
  * - swarmTools - Swarm orchestration tools
255
255
  * - SwarmError, DecompositionError - Error classes
256
256
  * - formatSubtaskPrompt, formatEvaluationPrompt - Prompt helpers
257
+ * - selectStrategy, formatStrategyGuidelines - Strategy selection helpers
258
+ * - STRATEGIES - Strategy definitions
259
+ *
260
+ * Types:
261
+ * - DecompositionStrategy - Strategy type union
262
+ * - StrategyDefinition - Strategy definition interface
257
263
  *
258
264
  * NOTE: Prompt template strings (DECOMPOSITION_PROMPT, etc.) are NOT exported
259
265
  * to avoid confusing the plugin loader which tries to call all exports as functions
@@ -266,6 +272,12 @@ export {
266
272
  formatSubtaskPromptV2,
267
273
  formatEvaluationPrompt,
268
274
  SUBTASK_PROMPT_V2,
275
+ // Strategy exports
276
+ STRATEGIES,
277
+ selectStrategy,
278
+ formatStrategyGuidelines,
279
+ type DecompositionStrategy,
280
+ type StrategyDefinition,
269
281
  } from "./swarm";
270
282
 
271
283
  /**
package/src/learning.ts CHANGED
@@ -64,6 +64,16 @@ export const CriterionWeightSchema = z.object({
64
64
  });
65
65
  export type CriterionWeight = z.infer<typeof CriterionWeightSchema>;
66
66
 
67
+ /**
68
+ * Decomposition strategies for tracking which approach was used
69
+ */
70
+ export const DecompositionStrategySchema = z.enum([
71
+ "file-based",
72
+ "feature-based",
73
+ "risk-based",
74
+ ]);
75
+ export type DecompositionStrategy = z.infer<typeof DecompositionStrategySchema>;
76
+
67
77
  /**
68
78
  * Outcome signals from a completed subtask
69
79
  *
@@ -85,6 +95,8 @@ export const OutcomeSignalsSchema = z.object({
85
95
  files_touched: z.array(z.string()).default([]),
86
96
  /** Timestamp when outcome was recorded */
87
97
  timestamp: z.string(), // ISO-8601
98
+ /** Decomposition strategy used for this task */
99
+ strategy: DecompositionStrategySchema.optional(),
88
100
  });
89
101
  export type OutcomeSignals = z.infer<typeof OutcomeSignalsSchema>;
90
102
 
@@ -435,4 +447,5 @@ export const learningSchemas = {
435
447
  CriterionWeightSchema,
436
448
  OutcomeSignalsSchema,
437
449
  ScoredOutcomeSchema,
450
+ DecompositionStrategySchema,
438
451
  };