systematic-debugging

Systematic debugging enforces a four-phase root-cause investigation workflow covering error reading, reproducibility checks, evidence gathering, and data-flow tracing. This structured approach identifies exact failure points before fixes, minimizing guesswork and rework.

Debug failing tests and production issues by following a four-phase playbook: gather evidence, verify reproducibility, trace data-flow, and implement fixes with regression testing guidance. This structured workflow applies across development, CI, and deployment environments to resolve unexpected software behavior.

Yes, the systematic debugging process applies to test failures, production bugs, and integration issues across development, CI, and deployment environments. It specifies a structured workflow with mandatory evidence gathering and regression testing guidance tailored for these contexts.

The best way to find a root cause is enforcing a disciplined investigation before proposing fixes. By gathering evidence, verifying reproducibility, and tracing data-flow through a four-phase process, you eliminate guesswork and avoid the rework caused by patching symptoms.

Yes, the debugging workflow can be delegated to a subagent workflow or integrated with test-driven development. This integration ensures regression safety by enforcing evidence gathering and providing regression testing guidance after resolving the root cause.

Gathering evidence and checking reproducibility before fixing a bug ensures you target the actual root cause rather than symptoms. This four-phase investigation prevents superficial patches, reduces rework, and establishes reliable conditions for subsequent regression testing.