Executes the implementation of features or fixes defined in a specification or ticket, utilizing TDD, type checking, and code review before committing changes to the current branch.
Quality gate: FAIL · better answers · measured 2026-10-23 Blind-judged against the bare model on 2 requests: average lift -8.0 points (specificity, structure, method, fit). won 0/2, lift -8.0, tokens ×346.19
Security scan: clean · 2026-10-24 · 2 files · ran in sandbox no network calls, shell tricks, credential access or instruction tampering found in its files.
Try asking
Say it in your own words; the assistant finds this recipe by itself. Examples:
“Implementér login-flowen beskrevet i ticket #402.”
“Byg brugerprofil-siden baseret på specifikationen i docs/profile.md.”
“Jeg har brug for, at betalingsgateway-integrationen bliver færdig. Her er ticketen: PAY-101.”
“Implement the login flow described in ticket #402.”
“Build the user profile page based on the spec in docs/profile.md.”
“I need the payment gateway integration done. Here is the ticket: PAY-101.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free
Do not use this skill for pure refactoring without new functionality, as that is better handled by a dedicated refactoring skill. It is not suitable for high-level architectural planning or creating the specification itself, which requires a planning or spec-writing skill. It should not be used for simple bug fixes that do not involve significant new logic or ticket references, where a quick patch skill might be more efficient.
Details
When it is the right choice
Use this skill when the user provides a specific ticket ID, a detailed specification, or a clear description of a feature to be built. It is appropriate for tasks that require writing new code, running tests, and committing the result to the repository. It is the primary action for turning requirements into working software.
The full recipe the assistant reads
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, ask.
Call the Skill tool with "tdd" where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Once done, call the Skill tool with "code-review" to review the work.
Commit your work to the current branch.
Files in this skill (3)
LICENSE
SKILL.md
agents/openai.yaml
Where it comes from
Vendored from mattpocock/skills, commit 5beb35b040e3, path skills/engineering/implement, licence MIT. The upstream licence file ships inside the skill.