Agent skill · data analytics · borghei
tech-debt-tracker
Scan codebases for technical debt with AST parsing, prioritize by impact, and generate trend dashboards. Use when tracking tech debt, prioritizing refactoring, calculating cost-of- delay, planning sprint debt, or reporting debt to execs.
Why this skill is useful
Adds 3 executable scripts for technical debt analysis and reporting that aren't in public docs.
What it needs
Requires python installed locally. About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Tech Debt Tracker The agent identifies, scores, prioritizes, and tracks technical debt across codebases using AST parsing, cost-of-delay analysis, and trend dashboards. Core Capabilities Detection — AST parsing (Python) and regex pattern matching (all languages) across six debt categories: code, architecture, test, documentation, dependency, infrastructure. Severity scoring — rate each item on velocity, quality, productivity, and business impact (1-10) plus effort sizing (XS-XL) and risk. Cost-of-delay — compute interest rate (Impact x Frequency) and cost of delay (Interest x Sprints x Team Multiplier); also WSJF and RICE frameworks. Prioritization — plot on the Cost-of-Delay vs Effort matrix (Immediate / Planned / Opportunistic / Backlog). Sprint allocation — apply the Debt-to-Feature ratio by team velocity; reserve capacity for debt work. Refactoring strategies — Strangler Fig, Branch by Abstraction, Feature Toggles, Parallel Run. Reporting — executive and engineering dashboards, trend analysis, velocity tracking, and forecasts from scan snapshots. When to Use Tracking and quantifying technical debt across a repository. Prioritizing refactoring work and calculating cost-of-delay. Planning sprint capacity allocation between debt and features. Reporting debt health, trends, and investment recommendations to execs. Clarify First Before scanning or reporting, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Target codebase — the directory to scan (the subject of the debt inventory) [ ] Prioritization framework & team size — cost-of-delay / WSJF / RICE and headcount (--framework, --team-size; changes the ranking and sprint allocation) [ ] Report audience — exec dashboard vs engineering inventory (sets the report format and altitude) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/tech-debt-tracker