Legacy Code Refactoring Prioritization Matrix

Role: Staff Software Engineer and Technical Debt Remediation Lead

Context

• Target codebase or module: {{codebase_module}}
• Known defect patterns and bug history: {{known_defects}}
• Current test coverage and automated safety nets: {{test_coverage_level}}
• Strategic business criticality: {{business_criticality}}
• Impact on engineering velocity: {{developer_velocity_impact}}
• Target delivery milestone: {{target_milestone}}

Task

Produce a technical debt audit and refactoring prioritization matrix for {{codebase_module}} that balances architectural health against delivery risks ahead of {{target_milestone}}.

Method

1. Deconstruct {{codebase_module}} into its core subcomponents, interfaces, and shared state layers.
2. Correlate {{known_defects}} with code complexity indicators (e.g., cyclomatic complexity, tight coupling, stale dependencies).
3. Assess {{test_coverage_level}} to determine regression danger for each target subcomponent.
4. Grade each refactoring candidate on an Impact scale (1-5) using {{developer_velocity_impact}} and {{business_criticality}}.
5. Grade each candidate on an Implementation Risk scale (1-5) based on blast radius and testing gaps.
6. Plot components into an Effort vs. Value prioritization matrix (Quick Wins, Strategic Investments, Defer, Avoid).
7. Outline incremental refactoring techniques (e.g., Strangler Fig, Branch by Abstraction) for top priorities.
8. Formulate a phased sprint execution schedule aligned with {{target_milestone}}.

Constraints

• MUST present the core output as a multidimensional prioritization matrix scored across effort, risk, and velocity gain.
• MUST establish explicit automated testing prerequisites before recommending destructive code changes.
• MUST NOT propose complete ground-up rewrites unless modular refactoring is proven unviable.
• Scores in the matrix must be fully justified by reference to {{known_defects}} and {{business_criticality}}.

Output format

1. Module Technical Health Summary (150 words diagnosing core debt in {{codebase_module}}).
2. Refactoring Prioritization Matrix (Table: Subcomponent, Risk Score, Impact Score, Refactoring Pattern, Priority Quadrant).
3. High-Priority Execution Blueprints (2-3 structured plans with prerequisite tests, pattern choice, and rollback plan).
4. Milestone Alignment Roadmap (Phased schedule mapped to {{target_milestone}}).

Self-review

• Ensure every subcomponent scored in the matrix has a clear dependency profile.
• Check that low {{test_coverage_level}} areas are flagged with higher risk scores.
• Confirm refactoring milestones are realistically achievable within {{target_milestone}}.