Skill Tracer
Skills › Skills For Real Engineers › implement

implement

skill · 17 lines · MIT · skills/engineering/implement/SKILL.md

The facts

Its description

Implement a piece of work based on a spec or set of tickets.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

This skill is not chosen from conversation: it carries `disable-model-invocation: true`, so the agent only runs it when the user invokes it directly (for example as /implement) with a spec or a set of tickets to implement. Nothing in the name or description lets the agent pick it up on its own.

A model's summary of when it is used.

A model's reading

Who can start it

Only you

Only you can start it. The agent never picks it on its own.

From its settingsline 4

What it leads to

Other skills this one hands off to, calls, requires or offers instead, as a model read them.

A model's reading

What leads to it

Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.

A model's reading

Licence

MIT, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text
Other files in this skill (1) Close

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: implement
3description: "Implement a piece of work based on a spec or set of tickets."
4disable-model-invocation: true
5---
6
8
9If the user passes a ticket reference, fetch it from the issue tracker and state its title before starting. If the reference is ambiguous, ask.
11Call the Skill tool with "tdd" where possible, at pre-agreed seams.
13Run typechecking regularly, single test files regularly, and the full test suite once at the end.
15Once done, call the Skill tool with "code-review" to review the work.
17Commit your work to the current branch.

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.

Raw lines 1 to 17
Names a skill to-spec :7
Names a skill tdd :11
Names a skill code-review :15

From mattpocock/skills at 4ae2317, 2026-10-31. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.