What problem does it solve? Random fixes and guess-and-check patching waste time, mask underlying issues, and introduce new bugs. This Skill enforces a disciplined root-cause-first debugging process so fixes address the actual problem instead of symptoms. ## Core Features & Use Cases - Four-Phase Process: Root cause investigation, pattern analysis, hypothesis testing, and verified implementation, with mandatory completion checklists per phase. - Tight Feedback Loops: Builds fast, deterministic, red-capable reproduction commands (failing tests, curl scripts, bisection harnesses, fuzz loops) before any fix is attempted. - Rule of Three & Architecture Escalation: After three failed fixes, stops and questions the architecture instead of attempting a fourth patch. - Use Case: A flaky integration test fails intermittently in CI. The Skill guides you to raise the reproduction rate, trace data flow across components, form ranked falsifiable hypotheses, and land a single regression-tested fix. ## Quick Start Use the systematic-debugging skill to investigate why the checkout endpoint returns a 500 error before proposing any fix.
