Tech Debt Tracker

Detect and prioritize technical debt across multi-repo codebases.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/theandyalvarez7-ruby/claude-skills --skill tech-debt-tracker-theandyalvarez7-ruby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Tech Debt Tracker
Source: https://github.com/theandyalvarez7-ruby/claude-skills/tree/main/engineering/tech-debt-tracker
Command: npx skills add https://github.com/theandyalvarez7-ruby/claude-skills --skill tech-debt-tracker-theandyalvarez7-ruby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Tech debt slows delivery, erodes code quality, and inflates maintenance costs; this skill provides a structured system to detect, analyze, and remediate debt at scale.

Core Features & Use Cases

  • Debt Scanner: automatically detects code debt signals across multiple languages using AST analysis and pattern matching, creating a comprehensive inventory.
  • Debt Prioritizer: computes CoD, WSJF, and RICE scores to surface high-impact items and guide sprint planning.
  • Debt Dashboard: tracks debt trends, health metrics, and executive-ready reports for visibility and accountability.
  • Use Case: A legacy payments service with high complexity and security debt can be scanned to surface critical items, prioritized into sprints, and monitored via dashboards.

Quick Start

Scan your repository to detect debt, prioritize the backlog, and review trends in the dashboard to start paying down the debt.

Frequently Asked Questions about Tech Debt Tracker

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

FAQPage Schema
How do I track technical debt across multiple repositories?

You can track technical debt across multi-repo environments by scanning codebases with AST analysis to detect debt signals, then centralizing the inventory into a dashboard for trend monitoring and stakeholder reporting.

How does automated tech debt detection work for cross-language stacks?

Automated tech debt detection works by applying AST analysis and pattern matching across cross-language stacks to identify code debt signals and generate a comprehensive inventory of maintenance issues.

What is the best way to prioritize technical debt for sprint planning?

The best way to prioritize technical debt is to compute Cost of Delay, WSJF, and RICE scores on detected debt items to surface high-impact tasks and guide structured sprint planning.

Can I generate executive-facing reports from my technical debt backlog?

Yes, you can generate executive-facing reports by tracking debt trends and health metrics in a dashboard, providing visibility and accountability for ongoing debt management and stakeholder communication.

Does automated debt tracking work for legacy services with high complexity?

Automated debt tracking works for legacy services by scanning complex codebases to surface critical security and complexity debt items, prioritizing them into sprints, and monitoring remediation via dashboards.

When do I need a technical debt tracker instead of standard code quality tools?

You need a technical debt tracker when managing debt at scale across multi-repo environments, requiring structured prioritization and executive reporting rather than just basic code quality linting.