Identifies, categorizes, and prioritizes technical debt, producing a scored backlog and phased remediation plan.
- What it does
- Guides an agent through a structured technical debt audit: it defines six debt categories (code, architecture, test, dependency, documentation, infrastructure) with examples and associated risks. It supplies a scoring framework where each item is rated on impact, risk, and effort, and priority is computed as (Impact + Risk) x (6 - Effort). The output is a prioritized list with estimated effort, business justification per item, and a phased remediation plan that can run alongside feature work.
- When to use it
- Use when a team asks what to refactor, wants a code health or technical debt audit, or needs to prioritize a maintenance backlog. It fits planning discussions about code quality and refactoring priorities.
- Requirements
- No scripts or tools; instructions only. It needs no packages, credentials, or network access beyond the agent itself.
Tech Debt Management
Systematically identify, categorize, and prioritize technical debt.
Categories
Prioritization Framework
Score each item on:
- Impact: How much does it slow the team down? (1-5)
- Risk: What happens if we don't fix it? (1-5)
- Effort: How hard is the fix? (1-5, inverted — lower effort = higher priority)
Priority = (Impact + Risk) x (6 - Effort)
Output
Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.
