matt-pocock-skills

A test-first plan converts ambiguous feature requests into verifiable outcomes by defining shared terms, outlining acceptance criteria, and breaking implementation into small slices with feedback loops.

Evidence-based debugging reduces wasted work by reproducing the failure first, isolating the failing boundary, and patching the smallest root cause rather than rewriting entire modules.

Architecture review without rewrite churn requires mapping module responsibilities and seams first, identifying proof requirements, and slicing changes into verifiable outcomes.

Test-first planning suits non-trivial implementation tasks by enforcing engineering alignment, clarifying assumptions, and requiring verifiable outcomes like failing tests or typechecks.

Test-first planning for ambiguous product work requires strict guardrails against invented requirements and skipped verification, meaning it cannot proceed without clarified assumptions or explicit questions.

Aligning a team on shared language involves capturing domain terms, abbreviations, and project-specific meanings early so the team converges on the same understanding before coding.