Vibe Debug

Overview

Turn rough reports about existing features into verified repairs. Reports, corrections, and retest results come from the user directing this session, in the conversation or in files they point to; keep their wording as evidence of experience, not proof of root cause, and take every other fact from the repository, its runtime, or an authoritative source named in references/source-routing.md. This workflow is self-contained; use available specialist capabilities only when helpful. Greenfield work, pure review, and history-only operations belong elsewhere.

Core Rule

Inspect available evidence before asking questions; ask only what changes the repair, proof, scope, or accepted risk. Treat free-text corrections to offered options as changed intent, not as the closest original option.