What problem does it solve? Random fixes and guess-and-check patches waste hours and introduce new bugs. This Skill enforces a disciplined four-phase debugging process that finds the root cause before any fix is attempted, preventing symptom-masking patches and repeated failed fix attempts. ## Core Features & Use Cases - Four-Phase Process: Root cause investigation, pattern analysis, hypothesis testing, and implementation, each with explicit completion criteria. - Tight Feedback Loops: Builds fast, deterministic, red-capable reproduction commands (failing tests, curl scripts, Playwright checks, bisection harnesses) before forming theories. - Rule of Three: After three failed fixes, stops and questions the underlying architecture instead of attempting a fourth patch. - Use Case: A production API returns intermittent 500 errors. Instead of guessing, you build a high-repetition repro loop, trace data flow across the service boundary, form ranked hypotheses, and land a single verified fix with a regression test. ## Quick Start Use the systematic-debugging skill to investigate why the checkout test fails before proposing any fix.
