summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt Pocock <mattpocockvoice@gmail.com>2026-10-29 10:42:51 +0000
committerGitHub <noreply@github.com>2026-10-29 10:42:51 +0000
commita496f5513d4a4cf889bc48e189e579f4b0bdf6aa (patch)
tree1da4243d9f13be3d8c98f3c742a130ff7af1ab72
parentd1478fcb140db0b93c0c8df17bcfd311844749d0 (diff)
implement-spec: a fresh implementer subagent per ticket (#1342)
* implement-spec: a fresh implementer subagent per ticket Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * implement-spec: a fresh merger subagent per merge Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * implement-spec: merger subagent need not be fresh Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
-rw-r--r--.changeset/implementer-fresh-per-ticket.md5
-rw-r--r--skills/engineering/implement-spec/SKILL.md4
2 files changed, 7 insertions, 2 deletions
diff --git a/.changeset/implementer-fresh-per-ticket.md b/.changeset/implementer-fresh-per-ticket.md
new file mode 100644
index 0000000..ac08d50
--- /dev/null
+++ b/.changeset/implementer-fresh-per-ticket.md
@@ -0,0 +1,5 @@
+---
+"mattpocock-skills": patch
+---
+
+`implement-spec` now uses a fresh implementer subagent for each ticket and for the code-review fixes, instead of reusing an earlier implementer.
diff --git a/skills/engineering/implement-spec/SKILL.md b/skills/engineering/implement-spec/SKILL.md
index 77bf59b..73d36c2 100644
--- a/skills/engineering/implement-spec/SKILL.md
+++ b/skills/engineering/implement-spec/SKILL.md
@@ -26,7 +26,7 @@ Communication to and from subagents should be sparse. Communicate primarily thro
3. Create the integration branch. If the issue tracker closes work through PRs, or the user asks for one, open a draft PR after the first merge in step 5 (a branch with no commits ahead of main can't open one), marked as closing the spec and tickets.
-4. Use **implementer subagents** to implement each ticket, each in its own worktree on its own branch. Each implementer subagent:
+4. Use a fresh **implementer subagent** for each ticket, each in its own worktree on its own branch. Each implementer subagent:
- confirms its worktree is based on the integration branch before starting, and resets onto it if not;
- calls the Skill tool with `tdd` to build the ticket;
- merges the integration branch tip into its own branch before reporting done
@@ -35,7 +35,7 @@ Communication to and from subagents should be sparse. Communicate primarily thro
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.
-7. Once all tickets are complete, call the Skill tool with `code-review` on the integration branch. Fix all issues raised by the code review in a single **implementer subagent**.
+7. Once all tickets are complete, call the Skill tool with `code-review` on the integration branch. Fix all issues raised by the code review in a single fresh **implementer subagent**.
8. If a draft PR exists, mark it ready for review. Otherwise, resolve each ticket the way the issue tracker closes work, and report the integration branch.