Turn recurring maintenance problems into a clear, prioritized cleanup list.
- TODOs and workarounds are scattered across a project.
- The same problems keep slowing down changes.
- You need to choose what cleanup work is worth doing next.
- Known problems, TODOs, or project files
- How each problem affects users or the team
- Time, staffing, and release constraints
Turn these maintenance problems into a prioritized cleanup backlog. Explain impact, effort, dependencies, and a sensible order.
- A grouped debt inventory
- Priority based on impact and effort
- Suggested sequencing and ownership
Priorities depend on real business and team constraints. By default, the workflow records debt in the host’s MEMORY.md Tech Debt Registry; confirm that location or request a report-only backlog when no memory file is available.
pi install npm:@firstpick/pi-skill-tech-debt-trackerRestart Pi if the skill does not appear in your current session.
See TECHNICAL.md for advanced usage, configuration, compatibility, and limitations.