opencode-onboard 0.1.12 → 0.1.13

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/steps/init-openspec.js +13 -11
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-onboard",
3
- "version": "0.1.12",
3
+ "version": "0.1.13",
4
4
  "description": "Prepare any brownfield codebase for AI agent workflows using OpenCode, OpenSpec, and ensemble orchestration.",
5
5
  "keywords": [
6
6
  "opencode",
package/src/steps/init-openspec.js CHANGED
@@ -29,14 +29,13 @@ const ENSEMBLE_PATCH = `6. **Implement via ensemble team**
29
29
  ...every task from tasks.md, one entry each...
30
30
  ]
31
31
  \`\`\`
32
- Save the task IDs returned. You MUST pass them to agents in step 6d.
33
32
  DO NOT proceed to 6d until team_tasks_add succeeds.
33
+ Do NOT call team_claim or interact with tasks further — the board is for visibility only.
34
34
 
35
35
  **Step 6d.** Spawn specialists ONE AT A TIME. Wait for each team_spawn result before calling the next.
36
36
  Each team_spawn MUST include agent field (required, causes NOT NULL error if omitted).
37
- Include: full task list, all context file paths, the task IDs for their tasks, and these instructions:
38
- - call team_claim with the task ID before starting each task
39
- - call team_tasks_complete with the task ID after finishing each task
37
+ Include: full task list and all context file paths. Tell each agent to:
38
+ - implement their tasks in order
40
39
  - send results to lead via team_message when all done or blocked
41
40
  \`\`\`
42
41
  team_spawn name:"back" agent:"back-engineer" prompt:"..."
@@ -51,16 +50,18 @@ const ENSEMBLE_PATCH = `6. **Implement via ensemble team**
51
50
  Do NOT call team_results, team_status, or team_broadcast in a loop.
52
51
  Teammates will message you when done or blocked. Wait for those messages.
53
52
 
54
- **Step 6f.** When teammates message back: call team_results to get full output,
55
- then team_shutdown + team_merge for each. Fix any blockers reported.
53
+ **Step 6f.** When teammates message back: call team_results to get full output
54
+ (team_message delivery is truncated — always use team_results for the full content).
55
+ Then for each teammate: team_shutdown → team_merge. Fix any blockers reported.
56
+ Do NOT edit any files between spawns and merges — team_merge blocks on overlapping local changes.
56
57
 
57
58
  7. **Quality check**
58
59
 
59
- Spawn quality engineer, wait for message back:
60
+ Spawn quality engineer with worktree:false (read-only, no file edits):
60
61
  \`\`\`
61
- team_spawn name:"quality" agent:"quality-engineer" prompt:"<task list, context files, run tests + build + lint + verify acceptance criteria, call team_claim/team_tasks_complete per task, send results to lead when done>"
62
+ team_spawn name:"quality" agent:"quality-engineer" worktree:false prompt:"<task list, context files, run tests + build + lint + verify acceptance criteria, send results to lead when done>"
62
63
  \`\`\`
63
- Wait for message → team_results → fix blockers → team_shutdown + team_merge
64
+ Wait for message → team_results → fix blockers → team_shutdown (no team_merge needed, worktree:false)
64
65
 
65
66
  8. **Mark tasks complete in openspec**
66
67
 
@@ -84,11 +85,12 @@ const ENSEMBLE_PATCH = `6. **Implement via ensemble team**
84
85
  - NEVER call team_spawn without the agent field — it is required and will fail without it
85
86
  - NEVER call team_spawn before team_tasks_add — tasks must exist before agents are spawned
86
87
  - NEVER poll team_results or team_status in a loop — wait for teammates to message you
87
- - NEVER claim or complete tasks as lead — only subagents call team_claim and team_tasks_complete
88
+ - NEVER call team_claim or team_tasks_complete — the task board is visual only, tasks.md is the source of truth
89
+ - NEVER edit files between team_spawn and team_merge — team_merge blocks on overlapping local changes
88
90
  - ALWAYS run team_cleanup force:true before team_create to clear stale state
89
91
  - ALWAYS add every task from tasks.md to the board with team_tasks_add before spawning
90
- - ALWAYS pass the task IDs returned by team_tasks_add to each agent's spawn prompt
91
92
  - ALWAYS spawn one at a time, waiting for each result before the next (avoids worktree contention)
93
+ - Do NOT instruct agents to call team_claim, team_tasks_complete, or any task board tool — agents only implement and report back via team_message
92
94
  - If teammates are stuck, use team_message to resend tasks, then wait — never implement directly
93
95
  - Mark tasks complete in openspec AFTER specialists finish, not before
94
96
  - Pause on errors, blockers, or unclear requirements. Do not guess