Debug

Structured debugging flow for functional bugs using specifications, logs, and observed behavior.

Input

Symptom: $ARGUMENTS

Investigation Steps

1. Restate the observed symptom — exact error message, stack trace, or unexpected behavior
2. Identify the smallest reproducible scope — minimal code that triggers the failure
3. Isolate assumptions — environment, input, state, concurrency
4. Inspect boundaries early — check validation and conversion points where external data enters
5. Distinguish implementation bugs from test bugs — dual-hypothesis approach
6. Verify the fix — rerun deterministic checks after fixing