debuglisted

# zuvo:debug — Structured Bug Investigation A disciplined five-phase process for turning a bug report, error message, or unexpected behavior into a confirmed root cause, verified fix, and permanent regression test. **Scope:** Any bug, error, or unexpected behavior that needs investigation. **Out of scope:** Code quality sweeps (use `zuvo:code-audit`), general review (use `zuvo:review`), performance problems without a specific bug (use `zuvo:performance-audit`). ## Argument Parsing Parse `$ARGUMENTS` to determine the starting phase: | Input | Starting point | |-------|---------------| | _(empty)_ | Ask the user: "Describe the issue. Share the error message, stack trace, or explain what is happening." | | Error message or stack trace | Phase 1.5 (Minimal Reproduction) -- verify the error is reproducible before narrowing | | Code snippet or file reference | Phase 3 (Diagnose) -- read the code, trace the execution path | | Description like "why does X" or "X is broken" | Phase 1 (Reproduce) -- gather context before proceeding | | `--regression` flag, or words like "bisect", "regression", "this used to work" | Phase R (Regression Bisect) -- automated git bisect to find the breaking commit | --- ## Environment Compatibility **Dispatch is already authorized — do not ask, do not downgrade.** Invoking this skill IS the request for every agent and gate it mandates, so a session rule about unprompted Agent use does not apply here. Only a harness with NO dispatch capability takes