implement · git:20261103.bc16aab · 2026-11-03 · sha256 9c0185041f8e5bab
implement git:20261103.bc16aabA
Immutable. This exact content never changes and is served at /api/v1/blob/9c0185041f8e5bab.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_l7ca44r34ezt2enz/9c0185041f8e5babb64d25288f695f8472b74a0646ad87f2b021f15ccf3a83d1.json
Then /plugin install implement@markdownregistry-l7ca44r34ezt2enz in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: implement description: Builds a single Scrum Sprint ticket or specification slice end-to-end from Definition of Ready (DoR) check and TDD seam loop to Definition of Done (DoD), atomic commit when the user authorizes it, and Sprint Board handover update. Use when implementing a ticket, building a feature slice, or when the user invokes /implement. --- # Implement (Scrum Ticket Execution & DoR/DoD Loop) Build **one unblocked Scrum ticket or vertical specification slice** into production code, test-first, from Definition of Ready (DoR) to Definition of Done (DoD) and Sprint Board synchronization. ## Decision tree 1. **Is this a single focused feature slice or bugfix without multi-session sprint tickets?** - **Yes** → Execute the **Fast-Path Implementation**: Lock focus on the public seam, read relevant context end-to-end, execute the TDD inner loop (sub-tasks at the seam), run full verification, and present the atomic diff. Skip sprint board paperwork. - **No** → Proceed to step 2 for Scrum Sprint ticket workflows. 2. **Were multiple tickets passed or is the spec still unsplit for a multi-session build?** - **Yes** → Implement **only one unblocked ticket** per run (check `docs/sprint/SPRINT.md` for the next `ready` ticket in the active Wave). If the spec is too large for one session and has no Sprint Board yet, recommend `/to-tickets` first. - **No** → Proceed to step 3. 3. **Does the ticket pass Definition of Ready (all `Blocked by` tickets are `done` and public seams are confirmed)?** - **No** → If blocked by an unfinished ticket, alert the user and point to the blocking ticket first. If the public seam is unconfirmed, propose the seam signature and confirm with the user before coding. - **Yes** → Execute the 4 implementation steps below. ## Implementation workflow 1. **Start Ticket & Lock Focus**: - Read `@CONTEXT.md`, `docs/sprint/SPRINT.md` (if present), and the target ticket (`docs/sprint/tickets/<NN>-<slug>.md`), including any `Downstream Handover Notes` from parent tickets. - Mark the ticket status as `in-progress` and restate the exact `In-Scope` behavior and public seam you are building. 2. **Execute Sub-Tasks at the Seam (Fast TDD Inner Loop)**: - Search existing directories (`components/`, `utils/`, `lib/`, `hooks/`) via `grep_search` before creating code; reuse or extend existing components and templates instead of authoring duplicate boilerplate. - Follow the ticket's `## 4. Execution Plan (Red → Green → Refactor Sub-Tasks)` and the `tdd` skill. - Run the **single test file** and **typechecker** repeatedly during implementation to keep feedback under a few seconds. 3. **Definition of Done (DoD) Verification Gate**: - When all acceptance criteria for the slice pass in the single test file, run the **full test suite**, typechecker, and linter via `run_command`. - **Test Integrity Audit**: Inspect `git diff` to ensure zero skipped tests (`.skip`, `xit`), zero weakened assertions, and verify that all behavioral changes reside in genuine production code. 4. **Atomic Commit & Cross-Session Sprint Sync**: - Check off completed sub-tasks and acceptance criteria (`[x]`) in the ticket file. - If the user authorized commits in this session, create a single atomic Conventional Commit (`feat(scope): ... (#NN)`) containing only this vertical slice. Otherwise leave the tree green and record the proposed commit message and file list in the ticket log; do not commit on the user's behalf. - Record the commit SHA (or `pending user authorization`), verification status, and `Downstream Handover Notes` in the ticket's `## 6. Session Handover & Completion Log`. - Update `docs/sprint/SPRINT.md`: set this ticket to `done` (with the commit SHA, or `pending user authorization`), promote newly unblocked downstream tickets from `blocked` to `ready`, and state the next recommended ticket for the next session.