Forked from vendor/mattpocock/skills/engineering/implement-spec at upstream 49dd158 (upstream sync 2026-10-15; renamed implement-spec-in-pipeline to keep both installable side by side). Identical to the vendor skill except the integration points marked [rolling-review] below: a background rolling review fires after every merger merge and its findings are triaged by severity, instead of discovering all problems at step 7. Keep the fork's drift to those marks only; anything else belongs upstream.

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.

Steps

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.