Software Technical Debt Allocation and Remediation Matrix

Role: Director of Engineering Operations specializing in agile capacity planning, codebase health, and developer velocity.

Context

• Engineering Organization: {{engineering_org}}
• Target Codebase Subsystems: {{codebase_modules}}
• Total Available Headcount: {{team_headcount}}
• Production Incident Frequency: {{incident_frequency}}
• Upcoming Strategic Milestone: {{growth_milestone}}
• Planning Cycle Duration: {{cycle_duration}}

Task

Design a technical debt remediation matrix for {{engineering_org}} that evaluates {{codebase_modules}} to balance maintenance work against feature delivery, ensuring stability for {{growth_milestone}} over {{cycle_duration}}.

Method

1. Evaluate historical defect trends and operational strain across {{codebase_modules}} relative to {{incident_frequency}}.
2. Quantify developer drag and deployment friction associated with each subsystem.
3. Determine blast radius and severity risk if each technical debt item remains unaddressed.
4. Calculate an Urgency Score (1-5) and Remediation Effort (in story points or staff-days) for each module.
5. Establish capacity thresholds across {{team_headcount}} (e.g., 70% features, 20% debt, 10% unallocated).
6. Allocate specific sprint capacity to high-scoring debt remediation tickets within {{cycle_duration}}.
7. Establish automated guardrails and test coverage KPIs to prevent technical debt recurrence.

Constraints

• You MUST assign an actionable remediation tactic to every item in {{codebase_modules}}.
• Total allocated remediation effort MUST NOT exceed 25% of total capacity across {{team_headcount}}.
• All scoring values must be explained via quantitative criteria rather than subjective impressions.
• Dependencies between feature releases for {{growth_milestone}} and debt remediation must be explicitly mapped.

Output format

1. Debt Categorization Model

A concise taxonomy defining severity levels (Critical, Severe, Moderate, Low) and capacity budget ratios.

2. Technical Debt Prioritization Matrix

A Markdown table containing the following fields: | Subsystem / Module | Debt Type | Production Risk (1-5) | Dev Velocity Drag (1-5) | Est. Effort (Days) | Remediation Strategy | Target Sprint | Owner Role |

3. Resource Allocation Summary

A concise tabular allocation breakdown illustrating sprint-by-sprint distribution of {{team_headcount}} across feature work vs. debt resolution for {{cycle_duration}}.

Self-review

• Ensure all subsystems from {{codebase_modules}} are accounted for in the matrix.
• Check that total remediation days do not violate the 25% capacity ceiling of {{team_headcount}}.
• Verify that critical dependencies for {{growth_milestone}} are addressed in early sprints.