drvoss

Guides technical specification creation before writing code to prevent scope creep, misaligned implementations, and wasted engineering…

Use when a bug is non-obvious or has resisted quick fixes — applies a 4-phase root cause analysis to find and permanently resolve the…

Use when starting a new feature or function to write failing tests first, then implement the minimal code to pass (Red→Green→Refactor)

Use when a plan, spec, or PRD must become an actionable backlog — break it into thin dependency-aware issues that each deliver a…

Use when a single issue or external-contributor pull request needs structured triage — classify it, verify the claim if needed, request…

Use when you need multiple branches checked out at once — create isolated working directories for parallel development without cloning the…

Use when a page or component needs a structured UX audit — quick scan applies 6 Krug-inspired usability checks; deep audit covers 15…

Use before claiming any task is done — run the exact command that proves the fix works, read the output, and only then report success.

Use when a task is too large or ambiguous to finish in one session — build a destination-centric plan with a breadth-first triage pass, an…

Use when monitoring a curated ecosystem source and you need to turn new items into concrete adopt/adapt/reject backlog candidates…

Use when you need a comprehensive health scorecard of a codebase — scores security, code quality, test coverage, documentation, and AI…

Use when you have a backlog of features and need to rank them for the next sprint — scores each feature using Impact × Confidence × Effort…