Tech Debt Assessment

Measure, prioritize, and address technical debt. Classify debt by impact and effort. Build paydown roadmap. Use when evaluating system health or planning refactoring.

48 stars 10 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill tech-debt-assessment
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/architecture-governance/skills/tech-debt-assessment ~/.claude/skills/tech-debt-assessment

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Tech Debt Assessment

Systematically measure technical debt, prioritize paydown, and track progress.

## Context

You are assessing technical debt in the system. Quantify impact (velocity reduction, risk increase), estimate effort to fix, prioritize based on ROI. Read code, metrics, team feedback.

## Domain Context

Based on technical debt frameworks (Steve McConnell, Martin Fowler):

- **Types of Debt**: Deliberate (knowingly cut corners for speed), accidental (poor design decisions), negligent (avoidable bad practices)
- **Impact**: Slows feature delivery (velocity decrease), increases bugs (quality risk), complicates future changes
- **Interest Payments**: Cost to maintain bad code; time spent working around it; bugs from complexity
- **Paydown**: Refactoring, rewriting, deprecating; costs time/resources upfront but reduces future interest

## Instructions

1. **Catalog Debt Items**: Interview team: "What slows us down?" Common themes: hard-to-test code, tangled dependencies, missing documentation, outdated libraries.

2. **Quantify Impact**: For each debt item, how much does it slow velocity? Example: "Test coverage < 30% makes refactoring 3x slower". Measure days/quarter lost to debt.

3. **Estimate Paydown Effort**: How long to fix? Refactor module: 2 weeks. Rewrite component: 1 month. Replace library: 3 days. Be realistic; add 50% buffer.
Read the full skill on GitHub

Details

Skill name
tech-debt-assessment
Path
architect/architecture-governance/skills/tech-debt-assessment/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Tech Debt Assessment skill do?

Measure, prioritize, and address technical debt. Classify debt by impact and effort. Build paydown roadmap. Use when evaluating system health or planning refactoring.

How do I install the Tech Debt Assessment skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Tech Debt Assessment popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.