systematic-debugging

Systematic debugging requires root cause investigation before proposing fixes. You need it for bugs, test failures, performance issues, and build failures where you might otherwise guess fixes and cause regressions.

Debug test failures by following a four-phase workflow: investigation, pattern analysis, hypothesis testing, and implementation. Form a single hypothesis, test it with minimal changes, and verify before applying any fix.

When debugging fixes fail, stop stacking patches. If a hypothesis fails, form a new one. After three failed fixes, trigger the escalation rule to re-analyze the issue or question the architecture.

Find the root cause of unexpected behavior by reading error messages, reproducing the issue consistently, and tracing failing data back to its original trigger during the investigation phase before suggesting changes.

Yes, systematic debugging applies to build failures and integration problems. It directs root-cause investigation across all failure types, preventing wasted time and new regressions under pressure.

Guessing fixes during debugging wastes time and introduces regressions. Systematic debugging enforces mandatory verification and single-hypothesis testing to prevent rationalizations and ensure the real root cause is fixed.