
This breaks down technical debt into six categories (code, architecture, test, dependency, documentation, and infrastructure) and scores each item using a formula that weighs impact, risk, and effort. The output is a prioritized backlog with business justifications and a phased remediation plan you can work through alongside feature development. It's most useful when you know something's wrong but can't articulate why refactoring X matters more than refactoring Y, or when you need to make the case to leadership that yes, we really do need to upgrade that ancient library. The scoring framework is simple enough to be practical without turning debt management into its own full-time job.
$ npx -y skills add anthropics/knowledge-work-plugins --skill tech-debt --agent claude-codeInstalls into .claude/skills of the current project.
Systematically identify, categorize, and prioritize technical debt.
| 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 |
Score each item on:
Priority = (Impact + Risk) x (6 - Effort)
Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.
Sponsors