tech-debt

To catalog technical debt, the Skill enumerates debt items across architectures, modules, and scripts, tagging each with severity, location, and category. This produces a structured inventory with prioritization data for scheduled remediation planning.

Prioritizing code refactor tasks requires estimated fix costs and severity tagging. The Skill generates a structured debt inventory with this data, enabling teams to decide what to clean up next and track progress over time at sprint boundaries.

You should run a tech debt audit at sprint boundaries or when deciding what to clean up next across your software architecture. Periodic debt audits help track progress over time and generate prioritized reports for scheduled remediation planning.

Yes, you can estimate fix costs for code quality issues across different modules. The Skill maps the location of debt items and applies severity tagging with estimated fix costs to enable accurate prioritization and scheduled remediation planning.

Yes, the tech debt analysis works with scripts and broad architectures. It discovers and documents debt across modules, files, and architectures, applying severity tags and estimated fix costs to produce a structured debt inventory for remediation planning.

You need a structured debt inventory for risk management because it provides prioritization data, severity tagging, and estimated fix costs. This enables scheduled remediation planning and helps decide what to clean up next across your codebase.