Stats
Actions
Tags
From engineering
Identifies, categorizes, and prioritizes technical debt across code, architecture, tests, dependencies, docs, and infrastructure. Scores by impact, risk, effort; outputs remediation plans.
How this skill is triggered — by the user, by Claude, or both
Slash command
/engineering:tech-debtThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematically identify, categorize, and prioritize technical debt.
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.
npx claudepluginhub anthropics/knowledge-work-plugins --plugin engineeringAssesses tech debt by identifying, classifying, and prioritizing maintainability problems to build a refactoring roadmap. Draws on twelve classic engineering books.
Analyzes codebases to identify and prioritize technical debt across code, architecture, testing, documentation, and infrastructure.
Systematically identify, classify, and prioritize technical debt in codebases using SQALE model and Fowler's quadrant. Guides static analysis, debt register creation, and ROI-based remediation.