Implement Spec

Implement spec

by mattpocock · MIT license · ★ 267,278 on GitHub · updated Sep 18

Implement the result of /to-spec and /to-tickets in code.

---
name: implement-spec
description: "Implement the result of /to-spec and /to-tickets in code."
disable-model-invocation: true
---

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.

Overview

You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.

Manual install (npx, ZIP)

Claude Codenpx skills add mattpocock/skills --skill implement-spec -g -a claude-code

Claude Code (degit)npx degit mattpocock/skills/skills/engineering/implement-spec#main ~/.claude/skills/implement-spec

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.7 KB

Read SKILL.md here

mattpocock/main1 file shown

SKILL.md2.7 KB

Browse every file on GitHub↗

SKILL.md

Show the full text41 lines

implement-spec/SKILL.md41 lines · 2.7 KB

PreviewCodeRawView on GitHub

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.
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:
- 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
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.

1	---
2	name: implement-spec
3	description: "Implement the result of /to-spec and /to-tickets in code."
4	disable-model-invocation: true
5	---
6
7	You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.
8
9	The issue tracker should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`.
10
11	The goal is the entire spec implemented on a single integration branch, with every ticket resolved the way the issue tracker closes work.
12
13	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.
14
15	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.
16
17	Implementer subagents should be run in the background where possible for maximum concurrency.
18
19	## Steps
20
21	1. Read the spec and tickets to understand the task graph.
22
23	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.
24
25	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.
26
27	4. Use implementer subagents to implement each ticket, each in its own worktree on its own branch. Each implementer subagent:
28	- confirms its worktree is based on the integration branch before starting, and resets onto it if not;
29	- calls the Skill tool with `tdd` to build the ticket;
30	- merges the integration branch tip into its own branch before reporting done
31
32	5. Once an implementer subagent completes, merge its work to the integration branch with a merger subagent.
33
34	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.
35
36	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.
37
38	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.
39
40	9. Clean up all implementer subagent worktrees.
41