skills.rest
miptah21
miptah21COMMUNITY
Explore all skills by this author →
GitHub

tech-debt-tracker

Scan codebases for technical debt and generate prioritized remediation plans.

2|Updated Apr 8, 2026
Search Tags:#code quality#refactoring#technical debt#remediation planning#codebase scanning#severity scoring#dependency risk
One-click install
npx skills add https://github.com/miptah21/skills --skill tech-debt-tracker-miptah21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-tracker
Source: https://github.com/miptah21/skills/tree/main/.agents/skills/tech-debt-tracker
Command: npx skills add https://github.com/miptah21/skills --skill tech-debt-tracker-miptah21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tech debt detection and prioritization is hard to do consistently, so projects either accumulate hidden risk or spend time refactoring without business justification.

Core Features & Use Cases

  • Codebase scanning with actionable signals: Identifies TODO/FIXME/HACK markers, oversized files and functions, duplication, test gaps, outdated dependencies, and documentation/infra debt indicators.
  • Severity scoring and structured manual review: Converts findings into a scored inventory across Code, Architecture, Test, Dependency, Documentation, and Infrastructure debt types.
  • Cost-of-Delay prioritization and remediation planning: Produces a ranked plan using severity × business impact ÷ effort and formats recommendations into sprint- and quarter-ready outputs.
  • Use Case: Before a major refactor, quickly understand what’s causing reliability or velocity drag, then schedule the highest-return remediation work.

Quick Start

Ask an agent to run a technical-debt scan of your repository, score findings by severity and effort, then output the top prioritized remediation items with a sprint and quarterly plan.

Frequently Asked Questions about tech-debt-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize technical debt remediation across a large codebase?▼

To prioritize technical debt remediation, scan your codebase for markers like TODO/FIXME, oversized files, and outdated dependencies, then score findings by severity and business impact to generate a ranked sprint or quarterly backlog.

What is cost-of-delay prioritization for code refactoring?▼

Cost-of-delay prioritization for code refactoring ranks technical debt items by calculating severity multiplied by business impact, divided by effort. This method identifies high-return cleanup work to schedule during sprint planning.

How do I assess technical debt before a major refactoring project?▼

Assess technical debt before refactoring by scanning the codebase to identify test gaps, duplication, and architectural risks. This converts hidden reliability issues into a structured, scored inventory to guide cleanup efforts.

Can technical debt scanning identify high-risk dependency vulnerabilities?▼

Yes, technical debt scanning identifies high-risk dependency vulnerabilities by evaluating outdated dependencies. It categorizes these findings under dependency debt and incorporates them into the prioritized remediation plan.

What types of technical debt can be identified during a codebase scan?▼

A codebase scan identifies six types of technical debt: Code, Architecture, Test, Dependency, Documentation, and Infrastructure. Findings include oversized functions, duplication, test gaps, and outdated dependencies.

How do I plan sprint cleanup work using a technical debt backlog?▼

Plan sprint cleanup work by converting scanned technical debt findings into a prioritized remediation backlog. The ranked output formats recommendations into actionable sprint-ready and quarter-ready tasks based on effort and impact.

Related Skills

Explore More Software Engineering Skills→
XinAlohaXinAloha
3

ponytail-debt

Scan source files for ponytail comments and generate a debt ledger.

Community
Basic
OreStudioOreStudio
25

agile-product-owner

Create and prioritize user stories across ORE Studio sprint and product backlogs.

Official
Basic
Tonybleything76Tonybleything76

Tech Debt Tracker

Scan codebases to identify, prioritize, and track technical debt.

Community
Advanced
jackmcintyrejackmcintyre

python-refactoring

Analyze Python code for complexity, duplication, and best practices.

Community
Intermediate