Skip to main content

tech-debt

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.

ソース情報

リポジトリ
anthropics/knowledge-work-plugins
ソースの最終更新活動
2026年2月24日 00:08
検出された SKILL.md の言語
英語
スター
29,826
フォーク
3,372

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
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.
GitHubで見る