Skip to content
Skills Library
Programming · Building & coding

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.

Repository
dotclaude ↗
Licence
MIT
Last repository change
06.11.2026

Assessment and security

81/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content16 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

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

implement this spec\work the tickets\
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

  1. CRITICAL: BDD at pre-agreed seams, review before commit
Original SKILL.md headings · 17 lines, 160 words
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

RepositoryScoreLicence
This page · FradSer/dotclaude81MIT
ericrisco/rsc-harness100MIT
yonatangross/orchestkit100MIT
sentimony/agentic-workflow100MIT
moberghr/mtk-agent-toolkit100MIT
michielvandermeer/skills100MIT
rossumai/claude-marketplace100MIT
userKael/rastro100MIT
yonatangross/orchestkit100MIT

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',…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.