Agent skill · Security

technical-debt-register

Document and prioritize a technical debt backlog with business impact, effort estimates, and resolution strategy. Use when asked to audit technical debt, create a debt register, prioritize tech debt for a quarter, document architectural shortcuts, or build a debt reduction roadmap. Produces a structured technical debt register covering debt inventory by category, business impact per item, effort and priority scores, top-item resolution plans, and a quarterly debt reduction roadmap.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill technical-debt-register --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 13 KB
Bundled scripts: none
Path: skills/technical-debt-register/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Technical Debt Register Skill Produce a complete technical debt register for a team or service. A debt register is not a complaint list — it is a prioritized, business-impact-aware inventory that lets an engineering team make deliberate choices about which debt to pay down, in what order, and with what expected return. Good debt management is not eliminating all debt. It is ensuring debt is visible, owned, and resolved when the interest cost exceeds the cost of fixing it. ## Required Inputs Ask for these if not already provided: - **Team or service name** — what team and/or service this register covers - **Known debt items** — list of known technical debt, or ask Claude to elicit them by asking about: legacy code, missing tests, outdated dependencies, architectural shortcuts, manual processes, observability gaps, security backlogs - **Tech stack** — language, frameworks, infrastructure (helps Claude categorise and score items correctly) - **Team size and velocity** — number of engineers and approximate story points or days per sprint (needed for effort estimates) - **Current quarter / planning period** — so the roadmap targets the right timeframe ## Output Format --- # Technical

What's inside
Steps it walks through
  1. Required Inputs
  2. Output Format
  3. Overview
  4. Debt Category Definitions
  5. Debt Register
  6. Scoring Method
  7. Category Breakdown
  8. Top 5 Priority Items — Resolution Plans
  9. TD-XXX: [Highest priority item name]
  10. TD-XXX: [Second priority item name]
  11. TD-XXX: [Third priority item]
  12. TD-XXX: [Fourth priority item]
  13. TD-XXX: [Fifth priority item]
  14. Debt Reduction Roadmap
Ships with 3 files
  • references/debt-pricing.md
  • references/worked-example.md
  • templates/debt-entry.md
More from pm-claude-skills
All skills →
About this skill
What does the technical-debt-register skill do?

Document and prioritize a technical debt backlog with business impact, effort estimates, and resolution strategy. Use when asked to audit technical debt, create a debt register, prioritize tech debt for a quarter, document architectural shortcuts, or build a debt reduction roadmap. Produces a structured technical debt register covering debt inventory by category, business impact per item, effort and priority scores, top-item resolution plans, and a quarterly debt reduction roadmap.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill technical-debt-register --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going