--- name: mattpocock-implement-spec description: "Implement a spec's ticket graph on one integration branch." license: MIT disable-model-invocation: true metadata: source: mattpocock/skills source-commit: 4ae2317ddb22b046e26455e4f9c9b3aaaf62212d upstream-name: implement-spec upstream-status: published adaptation: namespaced-port --- ## Skillz integration This is Matt Pocock's version. Skill references use the `mattpocock-` prefix. Read a referenced skill's `SKILL.md` through the host's skill loader or file tools. Map AskUserQuestion to the host's question tool and shell examples to its shell. Use delegation only when available and permitted by the active instructions; otherwise perform the same work sequentially and report that limit. The user's scope and repository rules govern setup, file writes, tracker changes, messages, schedules, publishing, merging, and cleanup. A skill invocation alone does not broaden the user's request. Preserve existing work and configuration. Verify provider examples against current primary documentation before use. 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 `/mattpocock-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. Start every subagent with a fresh context window. 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 1. Read the spec and tickets to understand the task graph. 2. (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. 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 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 `mattpocock-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 **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. 7. Once all tickets are complete, call the Skill tool with `mattpocock-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. 9. Clean up all **implementer subagent** worktrees.