dev-debuglisted

# Debug Structured 11-phase debugging: context → intake → investigate → analyze → research → fix plans → select → reproduction test → implement → verify → completion. ## Process **Phase tracking** — first action of the skill: call `TaskCreate` with these 11 items (status `pending`), then use `TaskUpdate` to set each phase `in_progress` at start and `completed` at end. On context compaction the task list remains visible — no risk of forgotten phases. 1. PHASE 0: Context Loading 2. PHASE 1: Problem Intake 3. PHASE 2: Codebase Investigation 4. PHASE 3: Root Cause Analysis 5. PHASE 4: Context7 Research 6. PHASE 5: Fix Plan Generation 7. PHASE 6: Plan Selection 8. PHASE 7: Reproduction Test 9. PHASE 8: Implementation 10. PHASE 9: Verification 11. PHASE 10: Completion ## PHASE 0: Context Loading > **Todo**: call `ToolSearch query="select:TaskCreate,TaskUpdate"` first — both tools are deferred and unusable without their schemas. Then call `TaskCreate` with the 11 phase items (see above). Mark PHASE 0 → `in_progress` via `TaskUpdate`. **Stack context** (optional, skip what doesn't exist): - Read CLAUDE.md `### Stack` section - Read `.claude/research/stack-baseline.md` **Project context** (optional, skip if not present): - Read `.project/project.json` → extract: - `stack` (framework, language, packages) - `endpoints` (method, path, auth) - `data.entities` (names, fields, relations) - Read `.project/project-context.json` (if present) → extract: - `context` (structure,