What problem does it solve?
Unmanaged technical debt slows development velocity, introduces hidden bugs, and makes codebases increasingly difficult to maintain over time, leading to wasted engineering effort and delayed feature releases.
Core Features & Use Cases
- Automated Debt Scanning: Detects common tech debt indicators including TODO/FIXME/HACK comments, deprecated code markers, duplicated code blocks, oversized files and functions, and outdated dependencies, then categorizes each finding into architecture, code quality, test, documentation, dependency, or performance debt.
- Manual Debt Entry: Add new technical debt items manually with custom descriptions, affected files, impact assessment, category, and estimated fix effort to capture debt not caught by automated scans.
- Prioritization & Reporting: Re-sorts all debt items by a calculated priority score (impact multiplied by encounter frequency, divided by fix effort) to identify high-impact items for sprint planning, and generates trend reports to track debt growth or reduction over time, flagging items stuck in the backlog for more than 3 sprints.
- Use Case: An engineering team preparing for a sprint can run a scan to catch new debt from the previous iteration, manually add any newly identified issues, prioritize the full debt register to select items to tackle in the upcoming sprint, and generate a report to share with stakeholders on overall codebase health.
Quick Start
Use the tech-debt skill to scan your current codebase for technical debt indicators and append the findings to your project's tech-debt-register.md file.