Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mattpocock/implement-spec
Implement a specification in code.
Passed 11 of 18 test cases with the skill, and 8 of 18 without it.
and 5 more in the full report
7 fixed8 passed either way7 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Implementer subagent A just completed ticket #10, which was blocking tickets #11 and #12. What action should the orchestrator take immediately after merging ticket #10?
| Checked | Without skill | With skill |
|---|---|---|
| The orchestrator evaluates the updated task graph frontier to identify newly unblocked tickets. | Passed | Passed |
| The orchestrator spawns new background implementer subagents for newly unblocked tickets. | Missed | Passed |
The instructions your model reads when the skill loads.
You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.
The issue tracker should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.
The goal is the entire spec implemented on a single integration branch, with every ticket resolved the way the issue tracker closes work.
The tickets are not a list of steps. They are a task graph with blocking relationships between them. This means there is always a frontier of tickets which are ready to be grabbed.
Communication to and from subagents should be sparse. Communicate primarily through context pointers: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.
Implementer subagents should be run in the background where possible for maximum concurrency.
Read the spec and tickets to understand the task graph.
(optional) Use an exploration subagent to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets implementer subagents focus on implementation rather than exploration.
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.
Use implementer subagents to implement each ticket, each in its own worktree on its own branch. Each implementer subagent:
tdd to build the ticket;Once an implementer subagent completes, merge its work to the integration branch with a merger subagent.
If this changes the frontier of available tickets, kick off more implementer subagents to work on the new tickets. This allows for maximum concurrency.
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.
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.
Clean up all implementer subagent worktrees.
test cases passed, vs 8 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.