mp-implement

---
name: mp-implement
description: Use when implementing a piece of work from a spec or set of tickets — TDD at agreed seams, regular typechecking, code review, then commit.
source: https://github.com/mattpocock/skills/blob/main/skills/engineering/implement/SKILL.md
generated: 2026-07-08T18:57:57.851Z
category: concept
audience: engineers
---

## When to use

- Implementing work described in a spec or a set of tickets
- You have a plan and want a disciplined build loop rather than ad-hoc coding
- You want TDD applied at pre-agreed seams, not everywhere blindly
- You want the work reviewed and committed once it's done

## Key concepts

### Spec- or ticket-driven

Implementation is bounded by the spec or tickets the user provides — build what they describe, not more.

### TDD at agreed seams

Use test-driven development where possible, at pre-agreed seams — not as a blanket rule on every line.

### Continuous verification

Run typechecking regularly and single test files regularly during the build; run the full test suite once at the end.

### Review then commit

Once the work is done, run a code review over it, then commit to the current branch.

## Gotchas

- Don't run the full test suite on every change — single files during, full suite once at the end
- TDD only at pre-agreed seams; don't force it everywhere
- Review the work before committing, not after
- Commit to the current branch — don't branch or push unless asked

---
Generated by SkillMake from https://github.com/mattpocock/skills/blob/main/skills/engineering/implement/SKILL.md on 2026-07-08T18:57:57.851Z.
Verify against source before relying on details.

File: ~/.claude/skills/mp-implement/SKILL.md