skills.rest
dbc-oduffy
dbc-oduffyCOMMUNITY
Explore all skills by this author →
GitHub

debt-triage

Verify technical-debt backlog items against current code and update priorities.

5|2|Updated Mar 20, 2026
Search Tags:#prioritization#tech debt#deduplication#structured workflow#backlog triage#git verification#PM decisions
One-click install
npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill debt-triage-dbc-oduffy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debt-triage
Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/debt-triage
Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill debt-triage-dbc-oduffy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams stop letting a growing tech-debt backlog rot in place by reviewing relevance, verifying status against the current codebase, and re-prioritizing for actionable PM decisions.

Core Features & Use Cases

  • Backlog verification against current code: Pre-checks likely “already fixed” items via git history, then dispatches per-system “Haiku agents” to confirm still-open vs already-fixed vs partially-addressed.
  • Prior-rejection awareness: Surfaces prior out-of-scope enhancement rejections that overlap with incoming items to avoid repeating failed proposals.
  • Deduplication across debt and bugs: Cross-references overlapping bug backlog entries (e.g., BS-* with DCH-/WAA- overlaps) to prevent duplicated effort.
  • LoE-weighted hot-zone identification: Uses completion logs filtered to tech-debt activity to detect festering subsystems or chronic avoidance areas for PM attention.
  • PM decision framing and backlog updates: Produces grouped triage results, prompts explicit close/reprioritize/YAGNI choices, then updates tasks/debt-backlog.md and writes new out-of-scope concept files when needed.

Quick Start

Ask the coordinator to run the debt-triage skill to review tasks/debt-backlog.md, verify each item, and return a prioritized set of actions and PM decisions.

Frequently Asked Questions about debt-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize a tech debt backlog for PM decisions?▼

Tech debt backlog prioritization for PM decisions requires verifying each item against the current codebase to confirm it is still open, then grouping results by actionability. This skill reprioritizes and deconflicts backlogs by cross-referencing git history and existing bug backlogs to produce grouped PM-ready triage outputs.

What is the best way to deduplicate overlapping tech debt and bug backlog items?▼

Deduplicating overlapping tech debt and bug backlog items involves cross-referencing debt entries against bug tracking logs to find shared identifiers. This skill prevents duplicated effort by matching overlapping bug backlog entries with debt items before finalizing reprioritization decisions.

Can I verify if a tech debt item is already fixed before scheduling a refactor?▼

Verifying if a tech debt item is already fixed involves pre-checking git history for recent changes to the affected subsystem. This skill dispatches per-system verification agents to confirm whether each backlog item is still-open, already-fixed, or partially-addressed before scheduling work.

When should I run a structured tech debt triage workflow?▼

A structured tech debt triage workflow should be run when open debt items exceed defined thresholds or immediately after major refactors. This skill applies on-demand to review tasks/debt-backlog.md and produce updated, deconflicted backlog states for project management.

How does tech debt triage handle prior out-of-scope enhancement rejections?▼

Tech debt triage handles prior out-of-scope enhancement rejections by surfacing overlapping historical proposals during the review process. This prevents repeating failed proposals by prompting explicit close, reprioritize, or YAGNI decisions for each item and writing new out-of-scope concept files when needed.

What limitations exist when identifying festering subsystems in a tech debt backlog?▼

Identifying festering subsystems in a tech debt backlog is limited by the availability of completion logs filtered to tech-debt activity. This skill requires reading tasks/debt-backlog.md and optionally cross-referencing tasks/bug-backlog.md to detect chronic avoidance areas accurately.

Related Skills

Explore More Software Engineering Skills→
khgs2411khgs2411
38

flow-curator

Manage backlog items and archive completed phases in .flow plan directories.

Community
Intermediate
hadi-nayebihadi-nayebi
1

programmer

Execute Android backlog items with Gradle tests and health checks.

Community
Advanced
ValyntValynt

catch-up

Summarize recent git history, open debt, and architectural decisions.

Official
Intermediate
li3pli3p

debt-scan

Identify and prioritize technical debt in a codebase for remediation planning.

Community
Intermediate