implement
/implement
Implements a piece of work from a spec or ticket set. Use when the user says \"implement this spec\", \"work the tickets\", or wants code written from an existing plan.
- Author
- FradSer ↗
- Repository
- dotclaude ↗
- Licence
- MIT
- Last repository change
- 06.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implements a piece of work from a spec or ticket set. Use when the user says \"implement this spec\", \"work the tickets\", or wants code written from an existing plan.
Triggers from the description
Original author description
Implements a piece of work from a spec or ticket set. Use when the user says \"implement this spec\", \"work the tickets\", or wants code written from an existing plan.
How it works
- CRITICAL: BDD at pre-agreed seams, review before commit
SKILL.md preview
--- name: implement description: "Implements a piece of work from a spec or ticket set. Use when the user says \"implement this spec\", \"work the tickets\", or wants code written from an existing plan." 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 issue tracker and state its title before starting. If the reference is ambiguous, use the AskUserQuestion tool to ask which ticket they mean, proposing the matching references as options. Use /mattpocock:bdd where possible, at pre-agreed seams. During the Automation phase, load `/mattpocock:tdd` (BDD-driven) for test quality, seams, and mocking guidance. Run typechecking regularly, single test files regularly, and the full test suite once at the end. Once done, use /mattpocock:code-review to review the work. ## CRITICAL: BDD at pre-agreed seams, review before commit Use `/mattpocock:bdd` where possible, one red-green slice at a time at pre-agreed seams. Load `/mattpocock:tdd` (BDD-driven) during the Automation phase for test quality, seams, and mocking guidance. When the work is done, run `/mattpocock:code-review` over it — a commit without the two-axis review is not finished work. Commit your work to the current branch.
Files in this package (2)
- SKILL.md 1 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · FradSer/dotclaude | 81 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| sentimony/agentic-workflow | 100 | MIT |
| moberghr/mtk-agent-toolkit | 100 | MIT |
| michielvandermeer/skills | 100 | MIT |
| rossumai/claude-marketplace | 100 | MIT |
| userKael/rastro | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
Database snapshot: 13.11.2026 · package version 87ca661984ca (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86implement-spec
Implement a specification in code. Use when the user wants to implement the result of /mattpocock:to-spec and /mattpocock:to-tickets, or asks to work a whole spec on one integration branch. - 90rc-implement
Implements tickets in dependency order — least code, tests, then the gate. Use to build a ticket. Do not use to author one (rc-tickets). - 100output-build-workflow
Implement an Output SDK workflow from a plan document. Use when the user asks to build, implement, or code a workflow from an existing plan, or after output-plan-workflow has produced a plan and the user is ready to build. - 90implement-spec-with-codex
Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer. - 100implement-spec
Use when a ticket DAG from a complete specification needs parallel execution into a green draft PR. Not for a settled ticket with no spec: use work. Not for ticket decomposition: use to-tickets. - 90feature
Implement a feature from a spec (docs/specs/NNN_<name>.md), a spec slice, or a GitHub issue: write the code and tests, run the checks, and stop with a working tree to review. --commit also commits; --pr also opens the PR and runs its review. Use for 'implement the auth spec',…