Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Measure, prioritize, and address technical debt. Classify debt by impact and effort. Build paydown roadmap. Use when evaluating system health or planning refactoring.
npx claudepluginhub sethdford/claude-skills --plugin architect-governanceHow this skill is triggered — by the user, by Claude, or both
Slash command
/architecture-governance:tech-debt-assessmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematically measure technical debt, prioritize paydown, and track progress.
Evaluate and prioritize technical debt to balance feature velocity with system health. Use when deciding what debt to address in upcoming sprints.
Identifies, quantifies, and prioritizes technical debt in codebases across code duplication, complexity, architecture flaws, testing gaps, documentation lacks, and infrastructure issues. Creates remediation plans.
Identifies, categorizes, and prioritizes technical debt across code, architecture, tests, dependencies, docs, and infrastructure. Scores by impact, risk, effort; outputs remediation plans.
Share bugs, ideas, or general feedback.
Systematically measure technical debt, prioritize paydown, and track progress.
You are assessing technical debt in the system. Quantify impact (velocity reduction, risk increase), estimate effort to fix, prioritize based on ROI. Read code, metrics, team feedback.
Based on technical debt frameworks (Steve McConnell, Martin Fowler):
Catalog Debt Items: Interview team: "What slows us down?" Common themes: hard-to-test code, tangled dependencies, missing documentation, outdated libraries.
Quantify Impact: For each debt item, how much does it slow velocity? Example: "Test coverage < 30% makes refactoring 3x slower". Measure days/quarter lost to debt.
Estimate Paydown Effort: How long to fix? Refactor module: 2 weeks. Rewrite component: 1 month. Replace library: 3 days. Be realistic; add 50% buffer.
Calculate ROI: Paydown cost vs interest savings. Refactor for 2 weeks (80 hours) to save 5 hours/quarter in reduced bugs and faster changes. Payoff: ~16 quarters (4 years).
Prioritize: High impact + low effort = do first. High impact + high effort = plan for next quarter. Low impact = defer or accept. Build paydown roadmap: 20% of sprint capacity for debt.