Software EngineeringEngineeringGold

Identify and prioritize technical debt in your codebase.

Technical Debt Analyzer

Codebase analysis, technical debt, refactoring

expertv5.0

Best for

▸Legacy codebase modernization roadmap with business impact prioritization
▸Post-acquisition technical due diligence debt assessment
▸Architecture erosion analysis for monolithic system decomposition
▸Critical security vulnerability debt prioritization in production systems

What you'll get

▸Categorized debt inventory with SQALE-method effort estimates, business risk scores, and specific refactoring patterns for each finding
▸Prioritized roadmap with quarterly milestones, resource allocation recommendations, and ROI projections for debt reduction initiatives
▸Architecture assessment report identifying layer violations, circular dependencies, and strangler fig migration patterns with implementation sequences

Expects

Codebase samples, architecture diagrams, dependency manifests, or detailed system descriptions with business context.

Returns

Structured technical debt inventory with categorized findings, effort estimates, business risk assessments, and prioritized refactoring roadmap.

What's inside

“You are a Technical Debt Analyst. You systematically identify, quantify, and prioritize technical debt across code, architecture, dependencies, infrastructure, and documentation dimensions to reduce risk and accelerate development velocity. - **Multi-dimensional assessment**: You scan six debt categ...”

Covers

What You Do DifferentlyMethodologyWatch For

Not designed for ↓

×Writing actual refactoring code or implementation
×Project management or sprint planning without technical analysis
×General code review or style guide enforcement
×Performance optimization without debt context

SupaScore

84.7▼

Research Quality (15%)

8.85

Prompt Engineering (25%)

8.35

Practical Utility (15%)

8.2

Completeness (10%)

8.25

User Satisfaction (20%)

8.4

Decision Usefulness (15%)

8.8

Evidence Policy

Standard: no explicit evidence policy.

technical-debtrefactoringcode-qualityarchitecturelegacy-codecode-smells

Research Foundation: 6 sources (1 academic, 4 industry frameworks, 1 books)

This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.