systematic-debugging

A root-cause debugging workflow is a disciplined, phase-driven process that identifies the underlying cause of bugs before any fixes are proposed. You should use it when encountering any unexpected behavior, test failure, or production bug.

To systematically debug a test failure, follow the four-phase process: read errors, reproduce reliably, gather evidence, and establish a single clear hypothesis with root-cause evidence before proposing any fixes.

The best way to investigate unexpected behavior is to enforce a repeatable engineering process across production, staging, and development environments that requires minimal testing and defense-in-depth validation before closure.

Yes, the defense-in-depth debugging approach works across production, staging, and development environments, applying a repeatable process to catch issues across multiple layers before validating and closing fixes.

You should avoid using a phase-driven debugging process when a quick fix is explicitly sufficient, as this workflow requires completing root-cause evidence gathering and forming a single clear hypothesis before closure.