Identify, categorize, and prioritize technical debt for smarter refactoring decisions.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "tech-debt" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/engineering/skills/tech-debt/SKILL.md 2. Save it as ~/.claude/skills/tech-debt/SKILL.md 3. Reload skills and tell me it's ready
Run a technical debt audit on this repository. Categorize issues by code complexity, duplicated logic, test coverage, dependency risk, and maintainability. List high, medium, and low priority items and recommend a remediation order.
A categorized technical debt list with priorities, refactoring order, and remediation recommendations.
Based on the following module descriptions and recent incident history, identify the top 3 parts worth refactoring next. Explain the risk, impact scope, expected benefit, and recommended approach for each.
A prioritized refactoring shortlist focused on high-value areas with decision rationale.
Re-rank this maintenance backlog by urgency, business impact, fix cost, and long-term maintenance value. Mark which items are technical debt, bug fixes, or infrastructure improvements.
A re-ranked maintenance backlog that clearly separates debt types and handling priorities.
Systematically identify, categorize, and prioritize technical debt.
| Type | Examples | Risk |
|---|---|---|
| Code debt | Duplicated logic, poor abstractions, magic numbers | Bugs, slow development |
| Architecture debt | Monolith that should be split, wrong data store | Scaling limits |
| Test debt | Low coverage, flaky tests, missing integration tests | Regressions ship |
| Dependency debt | Outdated libraries, unmaintained dependencies | Security vulns |
| Documentation debt | Missing runbooks, outdated READMEs, tribal knowledge | Onboarding pain |
| Infrastructure debt | Manual deploys, no monitoring, no IaC | Incidents, slow recovery |
Score each item on:
Priority = (Impact + Risk) x (6 - Effort)
Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.
Build weighted sales forecasts with scenario planning, commit splits, and gap analysis.
Embed Zoom meeting features into web apps with full or component-based integration.
Track hiring stages, update candidate status, and monitor pipeline counts.
Prepare compliant month-end journal entries with debits, credits, and support.
Analyze compensation bands, offer competitiveness, equity grants, and retention risks.
Decide when Zoom MCP fits and create a safe Claude setup plan.
Analyze multi-language technical debt and prioritize code quality improvements.
Analyze technical debt across codebases in multiple programming languages.
Connect CodeScene code health analysis to AI for quality and debt insights.
Generate a visual inventory of a codebase’s tech stack and infrastructure.
Analyze codebase health to find dead code, dependency cycles, and architecture drift.
Compare debt payoff strategies and estimate timeline and total interest.