Technical Debt Paydown Strategy

Develop a tech debt paydown strategy step by step.

Tech debt inventory:
{{debt_inventory}}

Team capacity: {{team_capacity}}
Business priorities: {{business_priorities}}

Think through systematically:

1. CATEGORIZATION: Group debt by type (code quality, architecture, infrastructure, testing)

2. IMPACT ASSESSMENT: Which items cause the most pain? Developer velocity? Incidents?

3. EFFORT ESTIMATION: How much work is each item? T-shirt size estimates.

4. DEPENDENCY ANALYSIS: Which items block others? What must be done first?

5. BUSINESS ALIGNMENT: Which debt items align with upcoming feature work?

6. QUICK WINS: What high-impact, low-effort items can build momentum?

7. PRIORITIZATION: Apply weighted scoring (impact * urgency / effort)

8. CAPACITY ALLOCATION: How much sprint capacity should go to debt?

9. TRACKING: How will we measure progress and celebrate wins?

10. ROADMAP: What is the quarter-by-quarter paydown plan?