debug-workflow

A hypothesis-driven debugging workflow structures investigation into five phases: Isolate & Gather Context, Generate Hypotheses, Iterative Investigation, Confirm Root Cause, and Fix & Verify. It guides users from failure onset to verified fixes through systematic investigation.

Debug complex multi-system bugs by gathering context, generating hypotheses, and applying controlled experimentation. This structured workflow defines escalation criteria and context-management practices to track hypotheses and preserve investigation state.

The best way to reproduce a failure scenario for root-cause analysis is to describe the failure, reproduce it with a minimal test case, and follow the hypothesis-driven phases to locate and fix the root cause.

Yes, the debugging workflow includes explicit escalation criteria to involve higher-tier agents when architectural changes are needed during the investigation.

Binary-search methodology applies to software triage by isolating failure points through controlled experimentation within the iterative investigation phase, efficiently narrowing down variables in complex multi-system bugs.

Hypothesis-driven debugging should not be used for simple, single-system errors where traditional error tracing quickly identifies the issue. It is designed specifically for complex, multi-system bugs requiring structured investigation.