skills.rest
zinohome
zinohomeCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt-prioritizer

Scores and ranks technical debt items by impact, risk, and effort into a prioritized backlog.

Updated Mar 16, 2026
Search Tags:#code quality#refactoring#technical debt#prioritization#backlog#engineering management#roi analysis
One-click install
npx skills add https://github.com/zinohome/RTMessage --skill tech-debt-prioritizer-zinohome
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-prioritizer
Source: https://github.com/zinohome/RTMessage/tree/main/.github/skills/tech-debt-prioritizer
Command: npx skills add https://github.com/zinohome/RTMessage --skill tech-debt-prioritizer-zinohome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams accumulate technical debt but lack a systematic way to decide what to fix first, leading to reactive firefighting and declining velocity. ## Core Features & Use Cases - Objective Scoring Rubric: Assigns 1-10 impact, risk, and effort scores with clear criteria, then computes a priority score using the formula (Impact * 2 + Risk * 1.5) / Effort. - Ranked Backlog with ROI Analysis: Produces a sorted tech debt inventory with detailed assessments, cost-benefit analysis, and implementation plans for top items. - Quarterly Paydown Planning: Generates a quarterly plan allocating 10-20% of engineering capacity, with owners, success metrics, and a review cadence. - Use Case: A team lead collects eight debt items (outdated dependencies, missing indexes, poor test coverage), scores them with the rubric, and produces a Q1 plan scheduling the highest-ROI fixes first. ## Quick Start Ask the AI to score and prioritize your team's technical debt items using the impact, risk, and effort rubric and produce a ranked backlog with a quarterly paydown plan.

Frequently Asked Questions about tech-debt-prioritizer

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

FAQPage Schema
How do I prioritize technical debt in my backlog?▼

Score each debt item on impact, risk, and effort using a 1-10 rubric, then compute priority as (Impact * 2 + Risk * 1.5) / Effort. Rank items by this score so high-impact, low-effort fixes rise to the top.

What is a good formula for scoring technical debt?▼

A practical formula is Priority Score = (Impact * 2 + Risk * 1.5) / Effort, where each factor is rated 1-10. This weights user and business impact highest while discounting items that require large effort.

How much engineering time should go to tech debt each quarter?▼

Allocate 10-20% of sprint capacity to debt paydown, typically structured as a quarterly plan with high-priority items first and quick wins for morale. Increase the budget if velocity declines, incidents rise, or onboarding slows.

When should you pay down technical debt versus defer it?▼

Pay down immediately when debt is a security vulnerability, causes frequent incidents, or blocks critical features. Defer items with low impact and risk, very high effort, or when better architectural alternatives exist.

How do I run a quarterly tech debt review process?▼

Collect new debt items in week one, score and prioritize them in week two, then plan capacity and success metrics in week three. At quarter end, measure incident reduction and velocity impact, and adjust the process.

Related Skills

Explore More Software Engineering Skills→
tianjianjiangtianjianjiang
1

smith-postmortem

Guide structured, blameless incident postmortems with root cause analysis and action-item tracking.

Community
Advanced
ronniepinnellronniepinnell

sprint

Review backlog items and prioritize work for upcoming sprints.

Community
Intermediate
MonumentalSystemsMonumentalSystems
17

quality-metrics

Define QA standards for test coverage, code quality, and defect metrics.

Official
Advanced
Rikinshah787Rikinshah787
5

ghost

Modernize legacy codebases using strangler fig patterns and incremental migration.

Community
Advanced