tech-debt

To track technical debt across multiple codebases, use the scan subcommand to identify indicators like TODOs, FIXMEs, and deprecated APIs. It maintains a centralized debt ledger with categories, effort estimates, and sprint targets for each project.

Technical debt prioritization computes scores for tracked debt items to recommend what to include in the next sprint. It evaluates structured debt entries using category-specific prioritization rules across Architecture, Code Quality, Test, Documentation, Dependency, and Performance Debt.

Scan your repository for code quality and technical debt indicators by running the scan subcommand. It detects TODOs, HACKs, duplicated code, large files, high-complexity functions, and deprecated APIs, then categorizes them into a structured debt ledger.

Yes, you can maintain a centralized technical debt ledger for sprint planning. The tool enforces structured debt entries with categories, affected files, and effort estimates, then suggests specific remediation items to target in your next sprint.

You can classify technical debt into six categories: Architecture Debt, Code Quality Debt, Test Debt, Documentation Debt, Dependency Debt, and Performance Debt. The scan subcommand automatically maps indicators like duplicated code and deprecated APIs to these classifications.

Generate a technical debt remediation plan by using the prioritize and report subcommands. These compute prioritization scores for your categorized debt ledger and output actionable recommendations for sprint planning across your projects.