systematic-debugging

Resolve stubborn debugging failures by applying a structured five-phase process: Evidence Collection, Classification, Hypothesis Formation, Single-Variable Testing, and Fix Validation. This framework prevents rash fixes and wasted cycles on recurring test failures.

Hypothesis-driven debugging is a five-phase resolution process using explicit gates and escalation rules to diagnose failures with evidence. Initiate this structured protocol after two consecutive failed fix attempts to prevent wasted diagnostic cycles.

Systematically debug failing test suites by applying single-variable testing and fix validation across QA and production-like environments. The structured process enforces evidence collection and classification to isolate root causes before applying fixes.

When debugging stalls on repeated failures, trigger escalation pathways and use diagnostic templates provided by the framework. These explicit escalation rules manage external dependency risks and guide structured diagnosis when standard resolution approaches fail.

Yes, the hypothesis-driven failure resolution workflow directly applies to CI loops and test-driven development environments. It provides explicit quality criteria and single-variable testing to validate fixes across development, QA, and production-like environments.