team-shinchan:systematic-debugging

Systematic root-cause debugging uses a four-phase process—investigation, pattern analysis, hypothesis testing, and implementation—to identify why failures occur without guessing.

To debug failing builds without guessing, follow a disciplined methodology using explicit hypotheses, traceable evidence, and anti-pattern awareness to systematically verify the root cause before fixing.

Investigate unexpected runtime behavior by progressing through four phases: gather evidence, analyze patterns, test explicit hypotheses, and implement a verified fix to ensure traceability.

Use 5 Whys and hypothesis testing during the pattern analysis and hypothesis phases to improve debugging reliability and systematically identify the root cause of failing tests or runtime errors.

Yes, this systematic debugging methodology applies to unexpected behavior across code, configurations, and data flows, requiring disciplined reasoning and traceable evidence to validate fixes.

Prevent anti-patterns like shotgun debugging by applying escalation rules and condition-based waiting, ensuring disciplined reasoning and traceable evidence validate the root cause before implementation.