debuglisted

# Debug > Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference. Diagnose bugs via structured investigation, reproduce with failing tests, then fix or plan. **Announce at start:** "Using debug to investigate the issue." **Core principle**: Understand first → test second → confirm with user → fix third. **On start: create tasks for phases 1–4 only** via `TaskCreate`: - Phase 1: Parse Input - Phase 2: Investigate - Phase 3: Write Failing Tests - Phase 4: Propose & Wait for User Decision ← HARD STOP Mark each task complete (`TaskUpdate`) only when phase fully done. **Never mark Phase 4 complete until user responded.** **After user responds to Phase 4**: create Phase 5 task (`TaskCreate`) for chosen path — "Fix Inline" or "Hand Off to /bdk:create-plan" — then proceed. --- ## Decision Flow ```dot digraph debug_flow { rankdir=TB node [shape=box, style="rounded,filled", fillcolor="#f0f0f0"] start [label="Phase 1\nParse Input", fillcolor="#d4edda"] investigate [label="Phase 2\nInvestigate"] tests [label="Phase 3\nWrite Failing Tests"] decide [label="Phase 4\nPropose & ASK USER\n(HARD STOP)", fillcolor="#fff3cd", shape=octagon] fix [label="Phase 5a\nFix Inline + Verify"] plan [label="Phase 5b\nHand off to /bdk:create-plan"] done [label="Done", fillcolor="#d4edda", shape=doublecircle] start -> investigate investigate -> tests tests -> decide decide -> fix [label="user: 'Fix now'"]