capability-assess-debt

Invoke the skill with an optional scope argument such as code, design, test, documentation, or infrastructure. It scans for debt indicators like TODO comments, complexity violations, missing tests, and outdated dependencies, then outputs a prioritized report.

Each item is scored with the formula Impact x (6 - Effort), where both factors range from 1 to 5. Scores of 15 or higher are High severity, 8-14 are Medium, and 7 or below are Low, favoring high-impact quick wins.

Yes. Pass the item as the choice argument, for example a description like missing error handling in the API layer. The skill skips detection and goes directly to categorization, scoring, and remediation recommendations.

No. Detection is read-only and never modifies files. The only write action is optionally recording an architectural decision through the composed capability-record-decision skill when high-severity items require one.

The skill degrades gracefully. It skips design and infrastructure checks that depend on those adoption files and reports only code-level debt such as code smells, duplication, test gaps, and documentation issues.