What problem does it solves?
This Skill eliminates time-wasting random fixes and quick patches that only mask underlying issues. It enforces a rigorous, four-phase framework to ensure you always find and fix the root cause of any technical problem, preventing costly rework.
Core Features & Use Cases
- Four-Phase Framework: Guides you through Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation, ensuring a thorough approach.
- Evidence-Based Debugging: Mandates gathering evidence and reproducing issues consistently before proposing any fixes, preventing guesswork.
- Pressure-Resistant Rules: Designed to prevent shortcuts and rationalizations, even under extreme time pressure or exhaustion, ensuring discipline.
- Use Case: When a critical production API is down, this skill forces you to resist the urge for a "quick fix" and instead systematically investigate the root cause, preventing future recurrences and saving significant revenue.
Quick Start
Example: Encountering a test failure
You: I'm using the systematic-debugging skill to investigate this test failure.
Phase 1: Root Cause Investigation (BEFORE any fix)
- Read error messages carefully, reproduce consistently, check recent changes.
- Gather evidence in multi-component systems (add diagnostic instrumentation).
- Trace data flow (use superpowers:root-cause-tracing if error is deep).
Phase 2: Pattern Analysis
- Find working examples, compare against references, identify differences.
- Understand dependencies and assumptions.
Phase 3: Hypothesis and Testing
- Form a single, specific hypothesis: "I think X is the root cause because Y."
- Test minimally (one variable at a time).
- If fix doesn't work, form a NEW hypothesis (DON'T add more fixes).
Phase 4: Implementation
- Create a failing test case (use superpowers:test-driven-development).
- Implement a single fix for the root cause.
- Verify the fix, ensure no other tests are broken.
- If 3+ fixes failed, STOP and question the architecture.
