Mattpocock

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Pre-landing PR review. (gstack)

Teach the user a new skill or concept, within this workspace.

Grill me about specs for the workflows I want to build, within this workspace.

Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Writing, exploit — shape raw material into an article, paragraph by paragraph.

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 seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

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 the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

Writing, explore — mine raw fragments, no structure yet.

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Use when you need to resolve an in-progress git merge/rebase conflict.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.