skills/skills/engineering

Engineering

Skills I use daily for code work.

• diagnose — Disciplined diagnosis loop for hard bugs and performance regressions: reproduce → minimise → hypothesise → instrument → fix → regression-test.
• grill-with-docs — Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline.
• triage — Triage issues through a state machine of triage roles.
• improve-codebase-architecture — Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
• setup-matt-pocock-skills — Scaffold the per-repo config (issue tracker, triage label vocabulary, domain doc layout) that the other engineering skills consume.
• tdd — Test-driven development with a red-green-refactor loop. Builds features or fixes bugs one vertical slice at a time.
• to-issues — Break any plan, spec, or PRD into independently-grabbable GitHub issues using vertical slices.
• to-prd — Turn the current conversation context into a PRD and submit it as a GitHub issue.
• zoom-out — Tell the agent to zoom out and give broader context or a higher-level perspective on an unfamiliar section of code.
• prototype — Build a throwaway prototype to flush out a design — either a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.