What problem does it solve? Technical debt accumulates silently through TODO comments, workarounds, and outdated dependencies, making it hard to know what to fix first. This Skill scans the codebase for debt indicators, maintains a structured debt register, and scores items so teams can schedule repayment deliberately. ## Core Features & Use Cases - Debt Scanning: Detects TODO, FIXME, HACK, and @deprecated markers, duplicated code, oversized files, and long functions, then categorizes findings into architecture, code quality, test, documentation, dependency, and performance debt. - Debt Register Management: Adds manual entries with category and effort estimates, and maintains a Markdown register at docs/tech-debt-register.md with user confirmation before every write. - Prioritization and Reporting: Scores items by impact, frequency, and fix effort, re-sorts the register, and generates trend reports flagging items older than three sprints. - Use Case: Before sprint planning, run a scan to catch new debt, re-prioritize the register, and feed the top items into the sprint plan. ## Quick Start Use the tech-debt skill to scan this codebase for debt indicators and write the findings to the debt register.
