Technical Debt Prioritization Matrix for Engineering Leads

Role: Senior Engineering Director specializing in enterprise software architecture and technical governance.

Context

• Target Team: {{engineering_team}}
• Core Subsystem: {{system_component}}
• Candidate Debt Items: {{debt_backlog_items}}
• Business Objectives: {{quarterly_okrs}}
• Organizational Risk Appetite: {{risk_tolerance}}

Task

Synthesize the provided backlog items into a structured Technical Debt Prioritization Matrix that scores each initiative against architectural risk, developer velocity drag, customer impact, and remediation effort to establish a defensible quarterly action plan.

Method

1. Review {{debt_backlog_items}} and map each item to the underlying components of {{system_component}}.
2. Evaluate how each debt item impairs or threatens {{quarterly_okrs}}.
3. Score developer friction and blast radius of potential failures based on {{risk_tolerance}}.
4. Estimate relative engineering effort (Low, Medium, High) for {{engineering_team}} to resolve each item.
5. Calculate a composite Priority Score (1-100) using weighted scoring across severity, customer exposure, and implementation complexity.
6. Assign a concrete recommendation status (Immediate, Next Quarter, Defer, or Monitor) for each entry.
7. Highlight operational trade-offs and critical dependencies between items.

Constraints

• MUST express the core deliverable as a Markdown comparison matrix with exactly six columns: Item Name, Architectural Risk, Velocity Drag, Remediation Effort, Priority Score, and Recommendation.
• MUST evaluate only the items listed in {{debt_backlog_items}} without inventing unrelated backlog tasks.
• Scores MUST adhere to a consistent 1-10 scale within matrix sub-evaluations before compiling the final Priority Score.
• Maximum word count for matrix cell annotations is 15 words per cell to ensure clean readability.

Output format

1. Executive Summary

• 2-3 sentence overview of portfolio debt health and resource allocation guidance for {{engineering_team}}.

2. Technical Debt Prioritization Matrix

• Markdown table containing columns: Debt Item, Architectural Risk (1-10), Velocity Drag (1-10), Remediation Effort (L/M/H), Priority Score (1-100), Recommendation.

3. Implementation Trade-Offs

• Bulleted list of top 3 architectural trade-offs and prerequisite remediation paths.

Self-review

• Confirm every debt item in {{debt_backlog_items}} appears in the matrix.
• Verify all Priority Scores logically reflect the individual risk and effort ratings.
• Ensure all MUST and MUST NOT constraints are strictly respected.