Implement (Matt Pocock skill)
Six lines, and that is deliberate. /implement takes a ticket or a spec and builds: it drives /tdd at pre-agreed seams, runs typechecking and single test files continuously, the full suite once at the end, then runs /code-review over its own work before committing to the current branch. It is the execution link of the main flow: one /implement per ticket, with a /clear between each, since every ticket is self-contained and the previous one's context is disposable.
Strengths
- Chains build, typecheck, test suite and review in a fixed order, without you asking again each time
- Drives /tdd internally at pre-agreed seams, so tests are not written after the fact
- Ends with a commit on the current branch: the work lands, it does not sit waiting in the context
- Short enough to read whole and adapt to your stack in five minutes
Limitations
- Assumes a ticket or spec already exists: with no /to-tickets upstream, it executes a fuzzy request
- Systematic commit on the current branch: if you are on main without noticing, that is where it commits
- Says nothing about ticket size: a ticket that is too big saturates the context mid red-green
Best for
- Devs who already have a ticket list and want to work through it without re-explaining the method
- Multi-session builds where each ticket is worked in a clean context window
- Teams who want every implementation to end reviewed and committed, with no exception