from draft30
Identify, categorize, and prioritize technical debt across six dimensions, producing evidence-based remediation plans and prioritized quick wins.
Performs a structured technical-debt analysis using a context-driven methodology. Scans code, architecture, tests, dependencies, documentation, and infrastructure to produce a prioritized report with effort estimates and remediation phases.
Run this skill when onboarding to a codebase, before major refactors, or when you need an evidence-based prioritization of technical debt to inform sprint planning and refactor tracks. Useful for maintainers, engineering managers, and architects.
Designed for code-review and automation agents that can access repositories and run CLI tooling (Claude Code, GitHub Copilot/gh, Cursor).
Tech Debt skill provides a thorough framework for identifying, categorizing, and prioritizing technical debt across six dimensions. No bundled scripts — purely prompt-driven. Well-structured with clear prioritization formula, remediation tiers, and cross-skill dispatch. Assumes /draft ecosystem context for full value but can run standalone with reduced analysis.
No scripts to test. Skill is entirely prompt-based — all analysis is done by the agent reading the codebase. The six-category framework is comprehensive. Cross-skill dispatch section is well-designed. No security concerns.
