implement-spec: merger subagent need not be fresh

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Matt PocockandClaude Opus 5.5 committed 2026-10-29 10:42:27 +00:00
1 parent 2db1fe46e4
commit afe8358918
2 files changed
+2 -2

No files matched your search

+1 -1
View File
@@ -2,4 +2,4 @@
"mattpocock-skills": patch
---
`implement-spec` now uses a fresh implementer subagent for each ticket and for the code-review fixes, and a fresh merger subagent for each merge, instead of reusing earlier ones.
`implement-spec` now uses a fresh implementer subagent for each ticket and for the code-review fixes, instead of reusing an earlier implementer.
+1 -1
View File
@@ -31,7 +31,7 @@ Communication to and from subagents should be sparse. Communicate primarily thro
- calls the Skill tool with `tdd` to build the ticket;
- merges the integration branch tip into its own branch before reporting done
5. Once an **implementer subagent** completes, merge its work to the integration branch with a fresh **merger subagent**.
5. Once an **implementer subagent** completes, merge its work to the integration branch with a **merger subagent**.
6. If this changes the **frontier** of available tickets, kick off more **implementer subagents** to work on the new tickets. This allows for maximum concurrency.