Tech Debt Triage
Score, prioritize, and plan technical debt remediation
Best use case
Tech Debt Triage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Score, prioritize, and plan technical debt remediation
Teams using Tech Debt Triage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tech-debt-triage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Tech Debt Triage Compares
| Feature / Agent | Tech Debt Triage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Score, prioritize, and plan technical debt remediation
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Tech Debt Triage Skill Score, prioritize, and plan technical debt remediation. ## Trigger Conditions - Sprint planning session - Quarterly tech debt review - User invokes with "triage tech debt" or "debt assessment" ## Input Contract - **Required:** Codebase metrics (churn, complexity, defect density) - **Optional:** Developer pain surveys, postmortem findings, code review history ## Output Contract - Scored and prioritized debt backlog - Quick wins identified (low effort, high impact) - Remediation roadmap with effort estimates - Contagion analysis (debt spreading to new code) ## Tool Permissions - **Read:** Code metrics, git history, defect tracker, postmortems - **Write:** Tech debt reports, backlog items - **Search:** Code hotspots and churn patterns ## Execution Steps 1. Collect code metrics: churn, complexity, defect density 2. Identify hotspots (high churn + high complexity) 3. Score each debt item: impact (blast radius), effort (team-days), contagion 4. Identify quick wins (effort <1d, impact >medium) 5. Check for recurring patterns from postmortems 6. Create prioritized backlog 7. Estimate remediation effort for top items ## Success Criteria - All debt items scored on 3 dimensions - Quick wins identified and flagged - Top 10 items have effort estimates - Contagion patterns identified ## Escalation Rules - Escalate if debt item blocks feature delivery - Escalate if contagion is spreading to >3 modules - Escalate if debt remediation requires >1 sprint of dedicated work ## Example Invocations **Input:** "Triage tech debt for the order processing module" **Output:** 14 debt items identified. Top 3: 1) OrderProcessor god class (impact: 9, effort: 3d, contagion: HIGH — 6 modules depend on it), 2) Missing retry logic in payment integration (impact: 8, effort: 1d, contagion: MEDIUM), 3) Hardcoded config values (impact: 5, effort: 0.5d, contagion: LOW — quick win). Remediation roadmap: sprint N (quick wins), sprint N+1 (retry logic), sprint N+2-N+3 (OrderProcessor decomposition).
Related Skills
email-triage-draft-replies
Review unread email, categorize it, and draft replies (no sending without approval)
analyze-japan-debt-service-tax-burden
以日本公債殖利率變化為觸發，量化「政府利息支出 / 稅收」負擔（含情境壓力測試），並判斷是否進入債務利息螺旋風險區。
agent-fintech-engineer
Expert fintech engineer specializing in financial systems, regulatory compliance, and secure transaction processing. Masters banking integrations, payment systems, and building scalable financial technology that meets stringent regulatory requirements.
writing-project-technical-writing
Writes technical prose (READMEs, ADRs, code comments) in the project's established human voice. Use when creating or editing .md files, writing Swift doc comments, authoring ADRs, or reviewing technical writing for voice consistency.
tech-news-digest
Generate tech news digests with unified source model, quality scoring, and multi-format output. Five-layer data collection from RSS feeds, Twitter/X KOLs, GitHub releases, Reddit, and web search. Pipeline-based scripts with retry mechanisms and deduplication. Supports Discord, email, and markdown templates.
Triage Workflow
This skill provides standardized workflows for rapid incident triage and initial assessment. For comprehensive triage procedures, decision trees, and real-world scenarios, please refer to the main **I
Technical Debt Prioritization
Technical Debt Prioritization enables systematic identification, measurement, and prioritization of technical debt for efficient remediation. This capability is essential for maintaining code quality,
Technical Content Marketing
* **Depends on**: None * **Compatible with**: None * **Conflicts with**: None * **Related Skills**: None # Technical Content Marketing
tech-stack
Specifies the technologies to be used for backend development, including Node.js, Express.js, MongoDB, and Mongoose.
tech-advisor
Recomienda stack tecnológico óptimo basado en requisitos del proyecto
dev-tech-debt-review
Detect AI/agentic-specific anti-patterns that traditional linters miss. Analyzes tool/agent boundary violations, prompt debt, context window issues, testing patterns, and more. Returns scored findings with remediation guidance.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.