tech-debt

Identify, classify, and prioritize technical debt items from engineering data sources.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/sahin/claude-skills --skill tech-debt-sahin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/sahin/claude-skills/tree/main/tech-debt
Command: npx skills add https://github.com/sahin/claude-skills --skill tech-debt-sahin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, prioritize, and plan technical debt paydown with impact-based classification, enabling engineering teams to reduce risk and accelerate delivery.

Core Features & Use Cases

  • Debt Identification: surface technical debt from code reviews, incidents, and documentation gaps.
  • Debt Classification (Fowler Quadrant): categorize debt as Deliberate vs Inadvertent and Reckless vs Prudent.
  • Impact Assessment: evaluate blocking features, incidents, development speed, onboarding, and growth of debt.
  • Prioritization: compute a priority score and schedule paydown.
  • Paydown Planning: allocate sprint capacity, bundle related items, and track progress.

Quick Start

Identify, classify, and prioritize the top technical debt items for the current project and generate a paydown plan.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I prioritize technical debt paydown across multiple codebases?

Technical debt prioritization applies impact-based classification, evaluating blocking features, incidents, and development speed to compute a priority score and schedule paydown across systems.

What is the best way to classify technical debt items from incident post-mortems?

Classifying technical debt uses the Fowler Quadrant model to categorize items as Deliberate vs Inadvertent and Reckless vs Prudent, surfacing debt from incidents, code reviews, and documentation gaps.

How do I plan sprint capacity for engineering debt paydown?

Planning debt paydown allocates sprint capacity by bundling related technical debt items, tracking progress, and scheduling prioritized tasks to reduce risk and accelerate delivery.

Can I use engineering health metrics to drive technical debt prioritization?

Yes, technical debt prioritization loads health metrics from engineering scorecards, architecture context, and runway data to drive impact assessment and prioritize paydown plans.

Does technical debt planning require a specific tech stack configuration?

Technical debt planning loads architecture context from tech stack files and debt registries, requiring engineering data sources to accurately assess impact and schedule paydown.