What problem does it solve? When an entire feature or module is broken, ad-hoc patching misses root causes and creates whack-a-mole bugs. This Skill enforces a systematic deep-dive repair process that maps the full feature boundary and dependency graph before any code is changed. ## Core Features & Use Cases - Five-Phase Protocol: Strictly ordered SCOPE, TRACE, DIAGNOSE, FIX, and VERIFY phases with a rule that no fixes may be proposed before diagnosis is complete. - Dependency Mapping: Traces inbound imports, outbound consumers, environment variables, config files, and database schemas to produce a complete dependency map. - Risk-Labeled Diagnosis: Classifies every issue as HIGH, MED, or LOW risk and requires confirmed root causes before fixing, with a 3-strike escalation rule that stops patching when fixes cascade into architectural problems. - Use Case: A user says "the authentication feature is broken, make it work." The Skill maps every file in the auth folder, traces all consumers like API routes and middleware, runs the related tests, produces a diagnosis report, fixes issues in dependency-type-logic-test order, and verifies all consumers pass. ## Quick Start Ask the AI to use the focused-fix skill to make the broken authentication feature work end-to-end.
