tech-debt-prioritization

Prioritizes technical debt items using RIME scoring to rank remediation work.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill tech-debt-prioritization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt-prioritization
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/tech-debt-prioritization
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill tech-debt-prioritization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a repeatable framework to identify, quantify, and prioritize technical debt so engineering teams can make data-driven trade-offs and allocate sprint capacity with measurable ROI.

Core Features & Use Cases

  • RICE prioritization: compute Reach, Impact, Confidence, and Effort to rank technical debt items by expected return.
  • Identification checklists: concrete code-level, architecture-level, and infrastructure-level indicators to detect and describe debt.
  • Planning and communication: sprint allocation strategies, cost-of-delay calculations, and a stakeholder-facing investment request template for justification.
  • Use Case: during sprint planning or quarterly roadmapping, score backlog debt items and select the highest RICE-return work to schedule or present to stakeholders.

Quick Start

Use the tech-debt-prioritization skill to scan listed debt items, assign Reach, Impact, Confidence, and Effort values, and return a ranked RICE-prioritized backlog.

Frequently Asked Questions about tech-debt-prioritization

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

FAQPage Schema
How do I prioritize technical debt items for sprint planning?

Prioritize technical debt by computing RICE scores from Reach, Impact, Confidence, and Effort inputs to rank refactoring work and produce a prioritized backlog for sprint planning.

What is the RICE framework for code refactoring prioritization?

The RICE framework scores technical debt items using Reach, Impact, Confidence, and Effort to quantify remediation work, enabling data-driven trade-offs and measurable ROI for refactoring investments.

How do I identify technical debt in a codebase for roadmapping?

Identify technical debt using concrete code-level, architecture-level, and infrastructure-level checklists to detect specific debt indicators before scoring and scheduling remediation during quarterly roadmap sessions.

Can I calculate cost of delay for technical debt remediation?

Yes, the skill includes cost-of-delay calculations alongside sprint allocation strategies to help quantify expected returns and trade-offs when scheduling refactoring or infrastructure upgrade work.

How do I justify technical debt refactoring to stakeholders?

Justify refactoring work using the included stakeholder-facing investment request template, which translates RICE scores and cost-of-delay calculations into a structured communication format for securing stakeholder approval.

Does technical debt RICE scoring work for infrastructure upgrades?

Yes, RICE scoring applies to infrastructure-level debt items, using specific checklists to describe upgrades and fixes, then ranking them by expected return for scheduling during sprint or roadmap planning sessions.