focused-fixlisted

# Focused Fix — Deep-Dive Feature Repair ## When to Use Activate when the user asks to fix, debug, or make a specific feature/module/area work. Key triggers: - "make X work" - "fix the Y feature" - "the Z module is broken" - "focus on [area]" - "this feature needs to work properly" This is NOT for quick single-bug fixes (use systematic-debugging for that). This is for when an entire feature or module needs systematic repair — tracing every dependency, reading logs, checking tests, mapping the full dependency graph. ```dot digraph when_to_use { "User reports feature broken" [shape=diamond]; "Single bug or symptom?" [shape=diamond]; "Use systematic-debugging" [shape=box]; "Entire feature/module needs repair?" [shape=diamond]; "Use focused-fix" [shape=box]; "Something else" [shape=box]; "User reports feature broken" -> "Single bug or symptom?"; "Single bug or symptom?" -> "Use systematic-debugging" [label="yes"]; "Single bug or symptom?" -> "Entire feature/module needs repair?" [label="no"]; "Entire feature/module needs repair?" -> "Use focused-fix" [label="yes"]; "Entire feature/module needs repair?" -> "Something else" [label="no"]; } ``` ## The Iron Law ``` NO FIXES WITHOUT COMPLETING SCOPE → TRACE → DIAGNOSE FIRST ``` If you haven't finished Phase 3, you cannot propose fixes. Period. **Violating the letter of these phases is violating the spirit of focused repair.** ## Protocol — STRICTLY follow these 5 phases IN ORDER `