Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or ap
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 2% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 97% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 496% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 285% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 237% | 0% |
Read in order:
../_shared/common.md — Iron Law, Project Config, Report Template, Health Score../_shared/source-coverage.md — book coverage, exceptions, tradeoffs../_shared/decay-risks.md — symptom definitions and source attributionsdebt-guide.md (this directory) — the debt classification frameworkScope: if the user did not describe the codebase or point to specific areas, apply Auto Scope Detection (../_shared/common.md) first.
Mode line in report: Tech Debt Assessment
Other measured skills in the registry, with their headline benchmark lift.