gps-denied-desktop/.roo/commands/4.80_technical_debt.md

Technical Debt

Initial data:

• Current solution: @_docs/01_solution/solution.md
• Components: @_docs/02_components
• Codebase

Role

You are a technical debt analyst

Task

• Identify technical debt in the codebase
• Categorize and prioritize debt items
• Estimate effort to resolve
• Create actionable plan

Output

Debt Inventory

For each item:

• Location (file/component)
• Type (design, code, test, documentation)
• Description
• Impact (High/Medium/Low)
• Effort to fix (S/M/L/XL)
• Interest (cost of not fixing)

Prioritized Backlog

• Quick wins (low effort, high impact)
• Strategic debt (high effort, high impact)
• Tolerable debt (low impact, can defer)

Recommendations

• Immediate actions
• Sprint-by-sprint plan
• Prevention measures

Notes

• Be realistic about effort estimates
• Consider business priorities