skills.rest
patricio0312rev
patricio0312revCOMMUNITY
Explore all skills by this author →
Website𝕏@patricio0312revGitHub

tech-debt-prioritizer

Score technical debt by impact, risk, and effort to create a ranked backlog.

5|Updated Dec 31, 2025
Search Tags:#refactoring#code-quality#tech-debt#technical-debt#roi-analysis#backlog-prioritization
One-click install
npx skills add https://github.com/patricio0312rev/skillset --skill tech-debt-prioritizer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-prioritizer
Source: https://github.com/patricio0312rev/skillset/tree/main/templates/architecture/tech-debt-prioritizer
Command: npx skills add https://github.com/patricio0312rev/skillset --skill tech-debt-prioritizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical debt often accumulates, slowing feature delivery and destabilizing systems. This Skill provides a structured approach to quantify, rank, and pay down debt to restore velocity and quality.

Core Features & Use Cases

  • Scoring rubric for impact, risk, and effort to surface the most consequential debt items.
  • ROI-based backlog prioritization with quarterly paydown recommendations.
  • Use cases include planning refactors, removing bottlenecks, and aligning teams on debt payoff.

Quick Start

Run a quarterly debt review to generate a prioritized 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?▼

To prioritize technical debt, you score each item by its impact, risk, and effort to generate a ranked backlog. Applying ROI analysis to these scores yields actionable quarterly paydown recommendations for your team.

What is the best way to calculate ROI for refactoring code?▼

Calculating refactoring ROI involves scoring the impact and risk reduction of a debt item against the effort required to fix it. This framework generates a ranked backlog, maximizing the return on your code quality efforts.

When do I need a structured framework for tech debt paydown?▼

A structured tech debt paydown framework is needed when accumulating debt slows feature delivery and destabilizes systems. Running a quarterly debt review aligns teams on payoff strategies and restores development velocity.

How do I plan a quarterly technical debt review?▼

Plan a quarterly technical debt review by applying a scoring rubric to evaluate backlog items by impact, risk, and effort. This process generates a prioritized paydown plan with actionable refactoring and architecture improvement recommendations.

Can I use ROI analysis to align my team on architecture improvements?▼

Yes, using ROI analysis to align teams on architecture improvements works by quantifying the payoff of addressing specific debt. Scoring impact, risk, and effort creates a ranked backlog that objectively guides and justifies refactoring priorities.

Related Skills

Explore More Software Engineering Skills→
mosheshammoshesham

tech-debt-tracker

Scan codebases to identify, prioritize, and track technical debt.

Community
Advanced
sjmyuansjmyuan
7

refactor-planner

Generate step-by-step TDD-based refactoring plans for code cleanup and architecture improvements.

Community
Intermediate
SivanwolSivanwol

technical-debt-manager-php-laravel

Identify and quantify PHP/Laravel codebase technical debt via static analysis, churn data, and dependency health, producing sprint-ready roadmaps with prioritized actionable tasks, acceptance criteria, and risk flags.

Community
Advanced
dralgorhythmdralgorhythm
111

estimating-work

Estimate development effort using story points and T-shirt sizing.

Community
Intermediate