technical-debt-manager

Inventory technical debt across code quality, tests, and dependencies.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/sandalsoft/agent-skills --skill technical-debt-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-debt-manager
Source: https://github.com/sandalsoft/agent-skills/tree/main/tech-debt
Command: npx skills add https://github.com/sandalsoft/agent-skills --skill technical-debt-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as an expert technical debt analyst who helps engineering teams identify, quantify, and prioritize technical debt, turning invisible code health problems into actionable, sprint-ready roadmaps that balance velocity with long-term maintainability.

Core Features & Use Cases

  • Debt Detection & Classification across code quality, test debt, documentation debt, dependency debt, design debt, infrastructure debt, and performance debt.
  • Quantitative Analysis: Calculate debt metrics including cyclomatic complexity, code duplication rates, test coverage gaps, and dependency health scores.
  • Strategic Prioritization: Apply the Fowler Technical Debt Quadrant to categorize debt and align with sprint planning and business value.
  • Actionable Roadmaps: Generate sprint-ready work items with effort estimates, risk assessments, and business value justifications.
  • Trend Analysis & Governance: Monitor debt accumulation over time using git history and establish early warning systems.

Quick Start

Scan your codebase to inventory debt across all categories and generate a sprint-ready remediation plan.

Frequently Asked Questions about technical-debt-manager

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

FAQPage Schema
How do I identify and prioritize technical debt for sprint planning?

To identify technical debt for sprint planning, inventory your codebase across code quality, test coverage, and dependencies, then apply a risk-based prioritization model like the Fowler Quadrant to categorize items by impact and effort. This generates a sprint-ready roadmap with actionable tasks.

What is the Fowler Technical Debt Quadrant and how does it classify code debt?

The Fowler Technical Debt Quadrant is a strategic prioritization model that classifies code debt into categories based on impact and effort. It helps engineering teams distinguish between reckless and prudent debt, aligning remediation tasks with business value during sprint planning.

How do I calculate technical debt metrics like cyclomatic complexity and test coverage gaps?

Calculating technical debt metrics involves analyzing your codebase to measure cyclomatic complexity, code duplication rates, test coverage gaps, and dependency health scores. These quantitative metrics transform invisible architecture risks into measurable debt items for remediation roadmaps.

Can I track technical debt accumulation over time using git history?

Yes, you can track technical debt accumulation over time by analyzing git history to monitor trends. This establishes governance through early warning systems that detect when code quality, documentation, or infrastructure debt increases between sprints.

What's the best way to generate actionable refactoring tasks from code quality issues?

The best way to generate actionable refactoring tasks from code quality issues is to scan your codebase, quantify design and performance debt, and map each issue to a sprint-ready work item with effort estimates, risk assessments, and owner assignments.