tech-debt

The tech-debt skill is designed to help software teams systematically identify, categorize, and prioritize technical debt within their codebase and infrastructure. By analyzing code quality, architecture, tests, dependencies, documentation, and infrastructure practices, it provides a structured approach to uncover areas that slow down development, introduce risk, or create maintenance challenges. This skill addresses the common problem of accumulating technical debt, which can lead to slower feature delivery, higher bug rates, and difficulties in scaling systems over time.

The core capabilities of this skill include categorizing technical debt into distinct types such as code debt, architecture debt, test debt, dependency debt, documentation debt, and infrastructure debt. Each category comes with example issues and associated risks, providing a clear framework for teams to assess their codebase. The skill also includes a prioritization framework that scores items based on impact, risk, and effort, generating a numerical priority value that informs remediation planning. The output consists of a detailed, prioritized list of technical debt items with estimated effort, business justification, and phased recommendations that can be addressed alongside ongoing feature work.

This skill is particularly useful for engineering managers, tech leads, and developers who are responsible for maintaining code health and planning refactoring initiatives. It can be employed during technical debt audits, code reviews, or strategic planning sessions to ensure that high-risk or high-impact issues are addressed first. By providing actionable insights and a structured approach, the skill helps teams improve code maintainability, reduce risks associated with legacy systems, and optimize resource allocation for development efforts.