What problem does it solve? Random fixes and guess-and-check patches waste time, mask underlying issues, and create new bugs. This Skill enforces a disciplined methodology that finds the true root cause of any bug, test failure, or unexpected behavior before any fix is attempted. ## Core Features & Use Cases - Four-Phase Debugging Process: Structured workflow covering root cause investigation, pattern analysis, hypothesis testing, and verified fix implementation. - Root Cause Tracing: Backward tracing through the call stack to find where bad values originate, with guidance on adding stack trace instrumentation. - Escalation Safeguards: Red-flag detection and a rule to question the architecture after three failed fix attempts, preventing fix-stacking thrash. - Use Case: A test suite fails intermittently in CI. Instead of tweaking timeouts, apply the methodology to reproduce the failure, trace data flow across components, form a single hypothesis, and implement one verified fix with a failing test case. ## Quick Start Use the systematic-debugging skill to investigate why my test suite fails intermittently before proposing any fix.
