What problem does it solve?
This Skill prevents wasted time and recurring regressions by forcing an evidence-driven approach to bugs, test failures, flaky behavior, build and integration problems, and production incidents so you fix the root cause instead of masking symptoms.
Core Features & Use Cases
- Structured four-phase process: clear Phase 1 (investigation), Phase 2 (pattern analysis), Phase 3 (single-hypothesis testing), and Phase 4 (implementation) to ensure disciplined progress.
- Evidence-first techniques: reproduce reliably, add instrumentation at component boundaries, trace data flow back to the original trigger, and create minimal failing tests before changing behavior.
- Guardrails and escalation rules: single-hypothesis testing, stop-and-reanalyze mandates, limits on consecutive fixes, and guidance to question architecture when multiple fixes fail.
- Use cases: on-call production incident triage, flaky test elimination, multi-component integration debugging, and preventing symptom-driven hotfixes.
Quick Start
Load the systematic-debugging skill and start Phase 1 by reproducing the issue consistently, collecting diagnostic evidence across layers, then form a single testable hypothesis and validate it with the smallest possible change.
