Files
gps-denied-desktop/.cursor/commands/4.refactoring/4.80_technical_debt.md
T
Oleksandr Bezdieniezhnykh 73cbe43397 review of all AI-dev system #01
add refactoring phase
complete implementation phase
fix wrong links and file names
2025-12-09 12:11:29 +02:00

894 B

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