implement-spec
Implement a specification and its tickets in code on one integration branch.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- implement-spec
- description
- Implement a specification and its tickets in code on one integration branch.
- disable-model-invocation
- true
03 SKILL.md 正文
Implement Spec
Inputs and goal
Use the specification from to-spec, the implementation issues from
to-tickets, and the configured issue tracker. Follow
tracker-workflow.md to identify the tracker. If none
is configured, tell the user to run the setup flow and stop.
Implement the entire specification on one integration branch. Resolve every issue through the tracker's documented workflow.
Coordination
Track each issue's blockers. The frontier contains unstarted issues whose blockers have all been implemented and merged into the integration branch. These are ready to implement; tracker closure can wait for the final pull request.
Start every subagent with a fresh context
(inherit_context: false, no resume). Run implementers in the background
(run_in_background: true) where possible.
Communicate with subagents through context pointers to the specification, issues, research notes, and prior commits. Do not duplicate content a pointer already reaches.
Steps
- Read the specification and issues, and identify each issue's blockers.
- When research would help, you can run one exploration subagent. Save Markdown notes outside the repository where later subagents can read them. Use a write-capable subagent, or have read-only Explore return findings and write the notes from the parent.
- Create the integration branch. Open a draft pull request only when the tracker closes work through pull requests or the user asks for one, and only after the first merge in step 5. Include the provider's closing references for the specification and implementation issues.
- Run one implementer subagent per ready issue, each in its own worktree and
branch. Have each implementer:
- Confirm its worktree is based on the integration branch, and reset onto it if not.
- Load
../tdd/SKILL.mdto build the issue. - Merge the integration branch tip into its branch before reporting done.
- Use a merger subagent to merge each completed implementer branch into the integration branch.
- Identify the newly ready issues and run their implementers. Repeat until no issues are ready.
- When every issue is implemented, load
../code-review/SKILL.mdagainst the integration branch. Use one fresh implementer subagent to fix every finding. - If a draft pull request exists, mark it ready for review. Otherwise resolve each issue through the tracker's workflow and report the integration branch.
- Delete every implementer worktree.
Output
Report the integration branch, each issue's resolution, and the pull request URL when one exists.
04 同仓库更多 Skills
writing-for-agents
Reference for writing documents an agent consumes: skills, AGENTS.md or CLAUDE.md, and docs reached by a pointer. Invoke when creating or editing a skill or an agent instruction file, or when a document's pointer wording, load, or structure is in question. Do not invoke merely because the user mentions writing-for-agents, names a skill, or writes 'skill <word>'.
wizard
Generate an interactive bash wizard for steps only a human can perform. Invoke when the user asks for a script or wizard for manual setup: infrastructure provisioning, credentials or CI secrets, a third-party dashboard, or a one-off migration or cutover. Do not invoke for steps the agent can perform, or merely because the user mentions wizard, names a skill, or writes 'skill <word>'.
wait-what
Stop and re-pitch the last message in plain, simplified language.
to-tickets
Split an agreed specification into reviewable vertical-slice issues with explicit blockers, then publish them after confirmation.
to-spec
Turn the current conversation into a specification and publish it after confirmation.
to-pr
Create a pull request from the current branch.