Use tech-debt-register
Turn a pile of technical-debt complaints, TODOs and incident notes into a ranked register
Turn a pile of technical-debt complaints, TODOs and incident notes into a ranked register: each item with where it lives, the cost it imposes today backed by evidence, the size of the fix, a decision (pay now, schedule, accept or watch) with the trigger that reopens it, and an owner if one was given. It ends with the few items worth paying down this quarter and why.
Reach for it when the user asks for a tech debt register, a debt inventory or backlog, "what debt should we pay down", "prioritise our tech debt", or wants to make the case for refactoring time.
Install it
npx skilldrop-cli install tech-debt-register # Claude Code, your user folder
npx skilldrop-cli install tech-debt-register --project # Claude Code, this repo
npx skilldrop-cli install tech-debt-register --ide cursor # or kiro, codex, antigravity, copilot
It is part of the Dev team pack: --pack dev-team installs it with its neighbours.
Ask for it
Say it the way you would to a colleague. Requests like these route to it:
- "Build a tech debt register from these notes"
- "Which of our technical debt should we pay down this quarter?"
- "I need to make the case to my director for refactoring time. Here's what's wrong with the codebase."
- "Turn this TODO/FIXME grep into a prioritised debt backlog"
Requests like these belong to a different skill, so it shouldn't answer them:
- "Plan the migration from our monolith's Postgres 12 to 16 with a rollback"
- "Triage these 40 incoming bug reports by severity"
- "Clean up our Jira backlog: find duplicates and stale tickets"
If another skill answers instead, ask for this one by name: "use tech-debt-register".
Check what you get
A good result:
- Every cost has evidence or says it has none. No invented hours, incident counts, percentages or money.
- Every item has a place or is listed as unlocated.
- Every item has a decision and a trigger.
- The top of the list is defensible: evidenced cost, fix the team can finish.
- It fits a planning meeting. One table, one short lead-in.
Use something else when
- Planning how to carry out one large change. Use
migration-plan. - Sorting incoming bug reports. Use
bug-triage. - Cleaning up a tracker backlog of mixed work. Use
backlog-triage. - Business or delivery risks that are not about the code. Use
risk-register.
Next
- SKILL.md, the instructions the agent reads
- Its page on the site
- Related: backlog-triage, bug-triage, migration-plan, risk-register