implement-spec

Agent Skills › mattpocock/skills › implement-spec

implement-spec

GitHub

根据规格说明书和任务图，协调子代理并行实现功能。通过探索、编码、合并及代码审查流程，将需求转化为集成分支上的完整代码并更新工单状态。

skills/engineering/implement-spec/SKILL.md mattpocock/skills

触发场景

用户要求根据规格说明书实现功能需要解析任务依赖关系并执行多步开发流程

安装

npx skills add mattpocock/skills --skill implement-spec -g -y

更多选项

非标准路径

npx skills add https://github.com/mattpocock/skills/tree/main/skills/engineering/implement-spec -g -y

不安装直接使用

npx skills use mattpocock/skills@implement-spec

指定 Agent (Claude Code)

npx skills add mattpocock/skills --skill implement-spec -a claude-code -g -y

安装 repo 全部 skill

npx skills add mattpocock/skills --all -g -y

预览 repo 内 skill

npx skills add mattpocock/skills --list

SKILL.md

Frontmatter

{
    "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.

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.