Systematic Debugging

When to use

• User reports failure, regression, test failure, instability, or unexpected behavior.
• The user needs a reproducible diagnosis before any code fix.

Required inputs

• Observable symptoms (errors, stack traces, repro steps).
• Recent changes and recent deploy context.
• Environment details and execution constraints.
• Whether execution changes are allowed.

Deliverables

• A structured diagnostic plan and prioritized root-cause hypothesis.
• Evidence list (commands, logs, file paths, and observed outputs).
• Recommended fix plan only after root cause confirmation.
• Explicit partial/blocked status when data is insufficient.
• Include schema_version in machine-readable output contracts.