Systematic Debugging

A strict debugging workflow. Use when dealing with bugs, test failures, or unexpected behavior.

Three core purposes:

1. Fix the cause, not the symptom.
2. Prevent guess-based fixes.
3. Lock the failure with a test before fixing.

Hard Gates

These rules have no exceptions.

0. Attempt reproduction FIRST, before any analysis.
   • If you do not know how to reproduce the bug, stop and ask the user.
   • Use available tools (e.g., ask_user_question) to ask: "How can I reproduce this bug? What steps, inputs, or conditions trigger it?"
   • Do not proceed to analysis until you have either reproduced the failure or asked the user for reproduction guidance.