skills/skills/engineering

Engineering

Skills I use daily for code work.

User-invoked

Reachable only when you type them (disable-model-invocation: true).

• ask-matt — Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
• grill-with-docs — Grilling session that also builds your project's domain model, sharpening terminology and updating CONTEXT.md and ADRs inline.
• triage — Move issues through a state machine of triage roles.
• improve-codebase-architecture — Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
• setup-matt-pocock-skills — Configure this repo for the engineering skills (issue tracker, triage labels, domain doc layout). Run once per repo.
• to-issues — Break any plan, spec, or PRD into independently-grabbable issues using vertical slices.
• to-prd — Turn the current conversation into a PRD and publish it to the issue tracker.
• prototype — Build a throwaway prototype — a runnable terminal app for state/logic questions, or several toggleable UI variations.

Model-invoked

Model- or user-reachable (rich trigger phrasing so the model can reach for them).

• diagnosing-bugs — Disciplined diagnosis loop for hard bugs and performance regressions: reproduce → minimise → hypothesise → instrument → fix → regression-test.
• tdd — Test-driven development with a red-green-refactor loop. Builds features or fixes bugs one vertical slice at a time.
• domain-modeling — Actively build and sharpen a project's domain model — challenge terms, stress-test with scenarios, update CONTEXT.md and ADRs inline.
• codebase-design — Shared discipline and vocabulary for designing deep modules: small interfaces, clean seams, testable through the interface.