What problem does it solve? Engineering teams accumulate technical debt across code, architecture, tests, dependencies, documentation, and infrastructure, but struggle to decide what to fix first. This Skill provides a structured audit method that turns vague code-quality concerns into a prioritized, business-justified remediation plan. ## Core Features & Use Cases - Debt Categorization: Classifies findings into six types — code, architecture, test, dependency, documentation, and infrastructure debt — each with typical risks. - Prioritization Scoring: Scores each item on Impact, Risk, and Effort, then computes Priority = (Impact + Risk) x (6 - Effort) to rank the backlog objectively. - Phased Remediation Plan: Produces a prioritized list with effort estimates and business justification that fits alongside ongoing feature work. - Use Case: Ask for a technical debt audit of your repository and receive a ranked list of refactoring targets, such as outdated dependencies or missing integration tests, with rationale for each. ## Quick Start Ask the assistant to run a technical debt audit of this codebase and produce a prioritized refactoring plan.
