Tech Debt Tracker

Tech Debt Tracker scans codebases for technical debt, scores severity, tracks trends over time, and generates prioritized remediation plans. It provides three tools: a Debt Scanner, a Debt Prioritizer, and a Debt Dashboard, enabling data-driven decisions about code quality and maintenance.

✨ What it does

  • Scans codebases for debt signals and outputs a JSON inventory with summary counts.
  • Prioritizes debt items using cost-of-delay, WSJF, or RICE frameworks.
  • Generates sprint allocations and insights for planning.
  • Tracks debt trends over time with dated snapshots and produces executive-ready summaries.
  • Provides a classification framework and common pitfalls guidance.

🎯 When to use it

  • When users mention tech debt, code quality, or refactoring priorities.
  • When planning cleanup sprints or code health assessments.
  • When modernizing legacy code or estimating maintenance costs.
  • When needing to track debt trends and verify the impact of remediation efforts.

🚀 How to use

Trigger by asking to scan, prioritize, or track tech debt in a codebase. Provide the path to the codebase or inventory file. Run the provided scripts in sequence: scanner, prioritizer, dashboard. Example prompts:

Scan my codebase at /path/to/codebase for tech debt.
Prioritize the debt inventory using WSJF with a team size of 6.
Track debt trends from the snapshots folder.

📄 Output: Outputs JSON files: debt_inventory.json, debt_priorities.json, and dashboard reports (HTML/JSON) with prioritized backlog and trend summaries.

📦 Add this skill to Claude Code

# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills

# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/engineering/skills/tech-debt-tracker .claude/skills/tech-debt-tracker

Skill source: engineering/skills/tech-debt-tracker/SKILL.md

⚠️ Good to know

Requires Python 3 and the scripts must be run from the skill folder; the scanner's output is needed for prioritization, and dated snapshots are needed for trend tracking.

❓ FAQ

What frameworks does the prioritizer support?

It supports cost_of_delay (default), wsjf, and rice.

How do I verify a cleanup sprint reduced debt?

Re-run the scanner, add a new dated snapshot, and run the dashboard to confirm targeted categories' counts dropped.

What is the recommended workflow?

Scan the codebase, prioritize the backlog, and track trends over time using dated snapshots.

🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.