Skip to content
Development
Skill

/implement-spec

Implement a specification in code. Use when the user wants to implement the result of /mattpocock:to-spec and /mattpocock:to-tickets, or asks to work a whole spec on one integration branch.

From plugin
dotclaude
59687 skills7 agents4 commands3 MCP

Claude Code

$ npx -y skills add FradSer/dotclaude --skill implement-spec --agent claude-code

SKILL.md

implement-spec.SKILL.md
name: implement-spec
description: "Implement a specification in code. Use when the user wants to implement the result of /mattpocock:to-spec and /mattpocock:to-tickets, or asks to work a whole spec on one integration branch."
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 `/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:bdd" to define the ticket's Gherkin scenarios, then with "mattpocock:tdd" for the BDD-driven Automation red-green loop that implements them;
  • 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.

Read more
@fradser
Ships withdotclaude

A curated collection of 23 plugins for Claude Code, providing specialized agents, skills, and automation tools for development and productivity workflows.

59687 skills7 agents3 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
596
Star history of FradSer/dotclaude on GitHub, a chart by star-history.com

Other skills on dotclaude.

use-acpx

use-acpx

Use acpx as a headless ACP CLI for agent-to-agent communication, always inside an isolated SubAgent. Use when running coding…

@fradser@fradserInstall Skill
delegate

delegate

Delegates a self-contained task to a Google Gemini Managed Agent (Antigravity) running in a remote sandbox with code execution,…

@fradser@fradserInstall Skill
research

research

Runs a deep-research query on Google Gemini's deep-research managed agent and returns a cited report. This skill should be used…

@fradser@fradserInstall Skill
code-context

code-context

This skill should be used when the user asks to "understand a codebase", "get code context", "research a library", "explore a…

@fradser@fradserInstall Skill
get-context

get-context

Execute this when the user requests code context for a repository, library, or any natural-language code/technology question…

@fradser@fradserInstall Skill

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react6d252k
@facebook@facebookInstall Skill

Questions about implement-spec.

Which coding agents can use implement-spec?
implement-spec installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.