systematic-debugging

Systematic debugging enforces reproduction-first, root-cause analysis, and failing-test verification before any code modification. It mandates strict phase-based gates to isolate faults, preventing reactive guessing and structurally verifying fixes for complex software defects across distributed systems.

To stop recurring bugs, enforce an evidence-based debugging workflow with hard gates requiring single-hypothesis validation. This approach eliminates "while I'm here" refactoring by ensuring every fix passes a failing test that structurally verifies the root cause is addressed.

Identify root causes of cascading failures by applying specialized fault isolation procedures. The workflow includes advanced techniques to detect retry storms and connection pool exhaustion, ensuring you structurally verify the root cause through failing-test-first validation before modifying code.

Yes, this systematic debugging workflow includes structured blocker triage. It provides a comprehensive checklist to systematically resolve environment or dependency issues before declaring a task blocked, ensuring external factors are eliminated before investigating code defects.

You should not use strict evidence-based debugging workflows for trivial, immediately visible code corrections. The rigorous hard gates requiring reproduction, single-hypothesis validation, and failing-test verification are designed for persistent bugs, intermittent test failures, and complex fault isolation.