systematic-debugging

Root-cause debugging enforces evidence gathering and issue reproduction before applying fixes. You must complete a strict investigation phase to confirm data, preventing symptom-driven changes that often lead to recurring production failures.

Systematic debugging uses a four-phase framework—Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This process includes anti-pattern awareness and defense-in-depth guidance to help engineers resist shortcuts during high-pressure production incidents.

Structure your debugging session using four prescribed phases, requiring strict Phase 1 completion before making changes. Utilize anti-pattern awareness and reference templates like root-cause-tracing.md and defense-in-depth.md to enforce durable fixes.

The four phases are Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This framework requires strict Phase 1 completion, anti-pattern awareness, and defense-in-depth references to ensure durable fixes before code changes are made.

Yes, systematic debugging covers all technical issues including bugs, test failures, and unexpected behavior. It enforces root-cause investigation through four phases, ensuring pattern analysis and hypothesis testing are completed before any implementation changes.

You should avoid symptom-driven fixes when facing production failures or recurring bugs. Instead, use systematic debugging to enforce root-cause investigation, pattern analysis, and hypothesis testing before implementation to ensure durable, defense-in-depth solutions.