You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
49
30%
Does it follow best practices?
Impact
73%
1.43xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/code-refactoring-tech-debt/SKILL.mdDebt inventory taxonomy and cost assessment
Complexity threshold
100%
80%
Long method threshold
0%
100%
God class definition
0%
0%
Nesting threshold
0%
25%
Duplication quantified
50%
100%
Dollar cost calculation
100%
100%
Risk classification
100%
100%
YAML metrics dashboard
0%
100%
Python trend dict
0%
12%
Three-tier roadmap
40%
100%
All seven output sections
66%
100%
Prevention strategy and quality governance
Max complexity gate
75%
100%
Max duplication gate
62%
0%
Min coverage gate
87%
100%
CI pipeline checks
37%
100%
Two-approval review
100%
100%
Review test and docs requirement
100%
100%
Sprint allocation 20%
100%
100%
Debt budget increase limit
0%
100%
Debt budget reduction mandate
0%
0%
Three tracking tools named
100%
100%
Code standard method length
0%
0%
Code standard class length
0%
0%
Monthly success metrics
0%
75%
Incremental refactoring implementation strategy
Phase 1: Facade
33%
50%
Phase 2: Parallel service
83%
91%
Phase 3: Feature flag migration
83%
100%
Backward compatibility
100%
100%
Test before refactoring
100%
100%
Document architectural decisions
12%
37%
Measure impact with metrics
87%
100%
Method length standard
0%
25%
Class length standard
0%
0%
Complexity standard
0%
100%
Coverage standard
100%
100%
6a07b83
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.