ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a spec or set of tickets.
$ npx -y skills add mattpocock/skills --skill implement --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/implementContext preview
The summary Claude sees to decide when to auto-load this skill.
Implement a piece of work based on a spec or set of tickets.
name: implement description: "Implement a piece of work based on a spec or set of tickets." disable-model-invocation: true
Implement the work described by the user in the spec or tickets.
Use /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, use /code-review to review the work.
Commit your work to the current branch.
My agent skills that I use every day to do real engineering - not vibe coding. Developing real applications is hard. Approaches like GSD, BMAD, and Spec-Kit try to help by owning the process.
Get the whole plugin, auto-invokedRepo: mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding…
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.