Agent Skills
› anthropics/knowledge-work-plugins
› tech-debt
tech-debt
GitHub用于系统性地识别、分类和优先排序技术债务。涵盖代码、架构、测试、依赖、文档及基础设施等类型，提供基于影响、风险和成本的优先级评分框架，并输出包含业务理由的分阶段修复计划。
Trigger Scenarios
用户询问技术债务相关问题
请求进行技术债务审计
咨询代码重构优先级
评估代码健康状况
查询维护积压情况
Install
npx skills add anthropics/knowledge-work-plugins --skill tech-debt -g -y
SKILL.md
Frontmatter
{
"name": "tech-debt",
"description": "Identify, categorize, and prioritize technical debt. Trigger with \"tech debt\", \"technical debt audit\", \"what should we refactor\", \"code health\", or when the user asks about code quality, refactoring priorities, or maintenance backlog."
}
Tech Debt Management
Systematically identify, categorize, and prioritize technical debt.
Categories
| 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 |
Prioritization Framework
Score each item on:
- Impact: How much does it slow the team down? (1-5)
- Risk: What happens if we don't fix it? (1-5)
- Effort: How hard is the fix? (1-5, inverted — lower effort = higher priority)
Priority = (Impact + Risk) x (6 - Effort)
Output
Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.
Version History
- 6f13415 Current 2026-07-05 18:28
