debug

A structured root-cause investigation systematically traces symptoms to evidence using a multi-phase workflow. It analyzes software bugs, crashes, and test failures without applying fixes, producing a formal diagnostic report with reproduction steps and a recommended fix direction.

Diagnosing test failures without modifying code is achieved through read-only analysis and evidence gathering. A debugging expert agent performs binary search narrowing and hypothesis confirmation to isolate the root cause, ultimately generating a diagnostic report instead of applying patches.

Narrowing down unexpected behavior in production requires binary search narrowing to isolate variables. The investigation workflow progresses from initial symptom analysis through hypothesis confirmation, ensuring every conclusion is backed by a concrete evidence trail before documenting the root cause.

Yes, the debugging workflow stops at diagnosis and does not apply any fixes. It generates a final root-cause artifact and a swarm-report for escalation, explicitly recommending a fix direction for hand-off to the implementation stage rather than modifying code directly.

Yes, the diagnosis process applies to unexpected behavior across both development and production environments. It handles software bugs, crashes, and test failures uniformly by guiding the investigation from symptom identification to evidence collection within its three-phase workflow.