implement-spec

作者: mattpocock

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

npx skills add https://github.com/mattpocock/skills --skill implement-spec

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.

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 tdd to build the ticket;
    • 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 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.

來自 mattpocock 的更多技能

ask-matt
mattpocock
詢問哪個技能或流程適合你的情況。此儲存庫中使用者呼叫技能的導航器。
communicationresearchproductivity
chief-of-staff
mattpocock
Pursue a long-running goal in a single session by co-ordinating subagents.
productivityproject-managementcommunication
claude-handoff
mattpocock
將當前對話移交給一個全新的背景代理,該代理會立即接手處理工作。
codebase-design
mattpocock
設計深度模組的共享詞彙。當使用者想要設計或改善模組介面、尋找深化機會、決定接縫位置、讓程式碼更易於測試或AI導航,或其他技能需要深度模組詞彙時使用。
designdevelopmentcode-review
code-review
mattpocock
從固定點(提交、分支、標籤或合併基礎)開始,沿兩個軸審查變更——標準(程式碼是否遵循此儲存庫記錄的編碼標準?)與規格(程式碼是否符合原始問題/PRD 的要求?)。透過平行子代理執行兩項審查,並並排報告結果。當使用者想要審查分支、PR、進行中的變更,或要求「從 X 開始審查」時使用。
testingdevelopmentcode-review
design-an-interface
mattpocock
使用平行子代理為一個模組生成多個截然不同的介面設計。適用於使用者想要設計API、探索介面選項、比較模組形狀,或提到「設計兩次」的情況。
developmentdesignapi
diagnosing-bugs
mattpocock
針對難以解決的錯誤與效能回歸的診斷循環。當使用者說「診斷/除錯這個」,或回報某個東西損壞、拋出錯誤、失敗、緩慢時使用。
testingdevelopmentcode-review
domain-modeling
mattpocock
建立並精煉專案的領域模型。當使用者想要確定領域術語或通用語言、記錄架構決策,或其他技能需要維護領域模型時使用。
designdevelopmentdocument