What problem does it solve? Debugging under pressure often devolves into guess-and-check fixes that mask symptoms, waste hours, and introduce new bugs. This Skill enforces a disciplined process that finds the actual root cause before any fix is attempted. ## Core Features & Use Cases - Four-Phase Framework: Structured progression through Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation, with explicit gates between phases. - Anti-Rationalization Defenses: Red flags, common rationalizations table, and anti-patterns that catch shortcut behavior like "quick fix for now" or stacking multiple changes at once. - Escalation Rules: After three failed fixes, the process mandates stopping to question the architecture rather than attempting a fourth patch. - Use Case: A test fails intermittently in CI. Instead of adding sleep calls, you follow Phase 1 to reproduce consistently, gather evidence across component boundaries, trace the data flow, and fix the actual source of the race condition. ## Quick Start Ask the AI to apply the systematic debugging process to investigate a failing test or bug before proposing any fix.
