What problem does it solve? Technical debt accumulates silently in codebases through TODO comments, workarounds, and deprecated APIs, making it hard to track what needs fixing and when. This Skill scans for debt indicators, maintains a structured debt register, and prioritizes repayment so teams can make conscious decisions about what to fix each sprint. ## Core Features & Use Cases - Debt Scanning: Detects TODO, FIXME, HACK, and @deprecated markers, duplicated code, oversized files, and overly long functions, then categorizes findings into architecture, code quality, test, documentation, dependency, and performance debt. - Debt Register Management: Maintains a markdown register at docs/tech-debt-register.md with effort estimates, impact ratings, and priority scores for every entry. - Prioritization & Reporting: Scores items by impact and frequency divided by fix effort, recommends sprint candidates, and generates trend reports flagging items older than three sprints. - Use Case: Before sprint planning, run a scan to catch newly introduced debt, re-prioritize the register, and produce a report showing whether total debt is growing or shrinking. ## Quick Start Ask the assistant to scan this codebase for technical debt and update the debt register with prioritized findings.
