cmd-workflow-team-investigate

Hypothesis-driven debugging is a systematic method to identify root causes in complex software bugs. Use it when the root cause is unclear, requiring stepwise reproduction, hypothesis generation, and sequential validation to resolve.

To investigate a complex bug step by step, reproduce and characterize the failure, generate and rank 3-5 probable hypotheses, test them sequentially, stop at the root cause, and document the evidence for a formal root-cause report.

No, this workflow enforces a linear investigation flow that prevents parallel reasoning. You must test hypotheses sequentially, validating one before moving to the next, ensuring a structured and traceable root-cause identification process.

The best way to document evidence for a root-cause report is to capture exact error messages, environment details, and timing during reproduction, then record validation results sequentially as you test each ranked hypothesis.

Yes, hypothesis-driven debugging provides a structured fix and verification plan. It includes a clear root-cause explanation and outlines specific post-fix validation steps to verify the resolution.

Sequential validation prevents guesswork by enforcing a linear investigation flow. Testing ranked hypotheses one by one stops at the actual root cause, speeding resolution and ensuring accurate, evidence-based bug fixes.