focused-fix

Coordinate end-to-end feature repairs using a structured debugging process that maps scope, traces dependencies, and diagnoses root causes. A five-phase workflow sequences fixes from scope to verification, ensuring dependencies and runtime issues are resolved systematically rather than with patchwork solutions.

Dependency tracing is handled within a structured phase workflow that maps feature boundaries before diagnosis. By prioritizing dependency mapping early, the process isolates whether root causes stem from external dependencies, types, or internal logic before applying controlled fixes.

Risk escalation is needed when cascading issues during feature diagnosis indicate deeper architectural concerns. If tracing dependencies reveals that root causes span multiple scopes or threaten structural integrity, the process escalates the risk rather than applying localized logic fixes.

Verify integration checks by running validation at the end of the five-phase workflow. After prioritizing fixes across dependencies, types, and logic, the process executes verifiable integration checks to ensure the repaired feature works correctly across the entire codebase scope.

The phase workflow targets complex features where root causes span scope, dependencies, runtime, and tests. For small code quality fixes, this disciplined approach may be excessive, as it is designed to prevent patchwork fixes in deep-dive repairs across a codebase.