Assess, quantify, and prioritize technical debt using code analysis, metrics, and impact analysis. Use when planning refactoring, evaluating codebases, or making architectural decisions.

Technical Debt Assessment Table of Contents [Overview]( overview) [When to Use]( when to use) [Quick Start]( quick start) [Reference Guides]( reference guides) [Best Practices]( best practices) Overview Systematically identify, measure, and manage technical debt to make informed decisions about code quality investments. When to Use Legacy code evaluation Refactoring prioritization Sprint planning Code quality initiatives Acquisition due diligence Architectural decisions Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents [Technical Debt Calculator](references/technical debt calculator.md) Technical Debt Calculator [Code Quality Scanner](references/code quality scanner.md) Code Quality Scanner Best Practices ✅ DO Quantify debt impact Prioritize by ROI Track debt over time Include debt in sprints Document debt decisions Set quality gates ❌ DON'T Ignore technical debt Fix everything at once Skip impact analysis Make emotional decisions

technical-debt-assessment