---
id: gh-implement-spec
name: "implement-spec"
url: https://skills.yangsir.net/skill/gh-implement-spec
author: mattpocock
domain: ai-agent-orchestration-collaboration
tags: ["spec-implementation", "multi-agent", "task-graph", "pr-management", "code-review"]
install_count: 276100
rating: 4.90 (120 reviews)
github: https://github.com/mattpocock/skills/tree/main/skills/in-progress/implement-spec
---

# implement-spec

> 此技能将规格说明（spec）解析为带依赖关系的任务图，并调度多个实现子代理并行工作，自动合并分支、运行代码审查，最终生成完整的PR。它最大化并发度，减少人工协调，适合需要按规格快速交付复杂功能的开发场景。

**Stats**: 276,100 installs · 4.9/5 (120 reviews)

## Before / After 对比

### 规格实现的交付时间对比

**Before**:

在手动实现规格时，开发者需要逐个阅读任务、规划顺序、频繁同步进度，容易因依赖关系阻塞而延长项目周期，平均需要20小时才能完成10个任务的规格实现。

**After**:

此技能将规格解析为任务图，自动调度多个实现子代理并行工作，并自动合并与审查，显著缩短了PR产出时间，同等规模下仅需5小时。

| Metric | Before | After | Change |
|---|---|---|---|
| 实现时长 | 20小时 | 5小时 | -75% |

## Readme

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

The goal is a PR which implements the entire spec on a single branch.

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

1. Read the spec and tickets. Read enough 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 a branch, and a draft PR. The PR should be marked as 'closing' the spec issue and tickets.

4. Use **implementer subagents** to implement each ticket. Each implementer subagent should work in its own worktree, on its own branch.

5. Once an **implementer subagent** completes, merge its work to the PR 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, run /code-review on the PR branch. Fix all issues raised by the code review in a single **implementer subagent**.

8. Mark the PR as ready for review.

9. Clean up all **implementer subagent** worktrees.


---
*Source: https://skills.yangsir.net/skill/gh-implement-spec*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-implement-spec/markdown*