implement · git:20261017.1456344 · 2026-10-17 · sha256 43f3901a84bdeb8e
implement git:20261017.1456344A
Immutable. This exact content never changes and is served at /api/v1/blob/43f3901a84bdeb8e.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jaytfesc4lkgaaaq/43f3901a84bdeb8eed228c7b53efe125258beb33348007266eeb49439e219192.json
Then /plugin install implement@markdownregistry-jaytfesc4lkgaaaq 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: "Implement a piece of work based on a spec or set of tickets." disable-model-invocation: true --- Implement the work described by the user in the spec or tickets. If the user passes a ticket reference, fetch it from the configured tracker (or its file under `docs/plans/` when there is no tracker, by absolute path into the main checkout: `docs/plans/` is never committed, so a worktree has none) and state its title before starting. If the reference is ambiguous, ask. Call the Skill tool with "tdd" where possible, at pre-agreed seams. Run typechecking regularly (`TYPECHECK_CMD`), single test files regularly, and the full test suite (`TEST_CMD`) once at the end. Both commands live in `.claude/project.env`; an empty key means that check is off. Once done, review the diff against the spec or tickets: every acceptance criterion met, nothing built beyond them. Commit your work to the current branch. If that branch is the trunk (`GIT_TRUNK` in `.claude/project.env`, default `main`), create a branch with `scripts/worktree-create.sh <name>` and commit there instead.