tech-debt

No issues found
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.
LIVE SINCE
SIZE13.0 KB
FILES3
FINDINGS2
AUTHORanthropics
INSTRUCTIONS

Tech Debt Management

Systematically identify, categorize, and prioritize technical debt.

Categories

TypeExamplesRisk
Code debtDuplicated logic, poor abstractions, magic numbersBugs, slow development
Architecture debtMonolith that should be split, wrong data storeScaling limits
Test debtLow coverage, flaky tests, missing integration testsRegressions ship
Dependency debtOutdated libraries, unmaintained dependenciesSecurity vulns
Documentation debtMissing runbooks, outdated READMEs, tribal knowledgeOnboarding pain
Infrastructure debtManual deploys, no monitoring, no IaCIncidents, 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.

FILES
LICENSE11.3 KB
NOTICE.md236 B
SKILL.md1.4 KB
Digest 9d280901d73d0c3a66d8747b04ff36abc264be2c70ed55d3ba7cf5909d8cd4ea