tech-debt · anthropics — Claude Code skill: audit and rank technical debt
Sorts technical debt into categories and scores each item so you know what to fix first. Useful when the backlog feels endless.
npx skills add anthropics/knowledge-work-plugins --skill tech-debt -a claude-codeWhat tech-debt does
The skill walks your codebase and groups what it finds into six buckets: code, architecture, tests, dependencies, documentation, infrastructure. Each bucket carries its own failure mode, from slow feature work to security holes and rough incident recovery. Every item then gets three scores between 1 and 5 — how much it slows the team, what happens if it stays, and how hard the fix is. Effort is inverted, so a small cleanup outranks a big rewrite.
Priority comes out as (Impact + Risk) x (6 - Effort). You get a ranked list with effort estimates and a business case per line, plus a phased plan you can run next to feature work. The arithmetic is deliberately plain, which makes the argument about numbers instead of taste.
Nothing here runs linters or pulls coverage reports. The model assigns the scores from your code and whatever you tell it about the project. A repo with no tests and no docs will leave some categories thin, and that is expected — the audit only reflects what the code shows.
What it helps with
- spot modules that keep slowing delivery
- separate urgent refactors from cosmetic ones
- make the case for debt work to stakeholders
- break a large refactor into phases beside feature work
- flag outdated and abandoned dependencies
Example prompts for the agent
- Run a technical debt audit on this repo and rank the findings
- What should we refactor first?
- Assess code health and give me a phased remediation plan
How to install tech-debt
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill tech-debt -a claude-code2Manually: put the files in place
~/.claude/skills/tech-debt/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/tech-debt/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill tech-debt -a codex2Manually: put the files in place
.agents/skills/tech-debt/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill tech-debt -a cursor2Manually: put the files in place
.cursor/skills/tech-debt/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/knowledge-work-plugins tech-debt2Manually: put the files in place
.github/skills/tech-debt/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill tech-debt -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/knowledge-work-plugins --path engineering/skills/tech-debtManually: put the files in place
.devin/skills/tech-debt/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill tech-debt -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about tech-debt
How do I install tech-debt in Claude Code?
Run npx skills add anthropics/knowledge-work-plugins --skill tech-debt -a claude-code. The skill lands in ~/.claude/skills/tech-debt/SKILL.md.
What does tech-debt do?
It identifies technical debt, sorts it into categories, and scores each item on impact, risk and effort. The result is a ranked list with a remediation plan.
Which platforms support the skill?
Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Each platform has its own install command.
Source text
SKILL.md · Apache-2.0
--- name: tech-debt description: Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog. --- # Tech Debt Management Systematically identify, categorize, and prioritize technical debt. ## Categories | Type | Examples | Risk | |------|----------|------| | **Code debt** | Duplicated logic, poor abstractions, magic numbers | Bugs, slow development | | **Architecture debt** | Monolith that should be split, wrong data store | Scaling limits | | **Test debt** | Low coverage, flaky tests, missing integration tests | Regressions ship | | **Dependency debt** | Outdated libraries, unmaintained dependencies | Security vulns | | **Documentation debt** | Missing runbooks, outdated READMEs, tribal knowledge | Onboarding pain | | **Infrastructure debt** | Manual deploys, no monitoring, no IaC | Incidents, slow recovery | ## Prioritization Framework Score each item on: - **Impact**: How much does it slow the team down? (1-5) - **Risk**: What happens if we don't fix it? (1-5) - **Effort**: How hard is the fix? (1-5, inverted — lower effort = higher priority) Priority = (Impact + Risk) x (6 - Effort) ## Output Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.
© anthropics · Apache-2.0 · anthropics/knowledge-work-plugins