tech-debt-trackerlisted

# Tech Debt Tracker Skill Systematic tech debt management: scan for debt signals, classify by type, prioritize using cost-of-delay, and track trends over time. ## Workflow 1. **Scan** -- Identify debt signals across the codebase. See [debt-signals.md](debt-signals.md). 2. **Classify** -- Categorize each finding (code debt, design debt, test debt, dependency debt, documentation debt). 3. **Prioritize** -- Rank findings using cost-of-delay frameworks. See [prioritization.md](prioritization.md). 4. **Report** -- Generate a debt inventory with actionable recommendations. 5. **Track** -- Compare against previous scans to measure debt trajectory (increasing, stable, decreasing). ## Debt Classification | Type | Examples | |--------------|---------------------------------------------------| | Code | Long functions, deep nesting, duplicated logic | | Design | Tight coupling, missing abstractions, god objects | | Test | Missing coverage, flaky tests, no edge cases | | Dependency | Outdated packages, deprecated APIs, pinned EOL | | Documentation| Stale comments, missing API docs, wrong examples | ## Output Format ``` [DEBT] type=Code severity=HIGH file:line Signal: Function exceeds 80 lines with cyclomatic complexity 14 Cost-of-delay: Blocks feature X, increases bug rate in module Y Recommendation: Extract into 3 focused functions by responsibility Priority: STRATEGIC (high value, high effort) ``