skills.rest
MysMon
MysMonCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt-management

Identify, classify, and track technical debt with a structured taxonomy and RICE prioritization.

2|Updated Jan 16, 2026
Search Tags:#refactoring#code-quality#legacy-code#technical-debt#risk-prioritization#code-health#rice-score
One-click install
npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill tech-debt-management
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-management
Source: https://github.com/MysMon/Spec-Workflow-Toolkit/tree/main/skills/workflows/tech-debt-management
Command: npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill tech-debt-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break free from hidden code issues by systematically identifying, classifying, and prioritizing technical debt to guide focused refactors and debt paydown.

Core Features & Use Cases

  • Debt taxonomy covering design, code, test, documentation, dependency, and infrastructure debt with actionable detection cues.
  • Prioritization guidance using a RICE-like framework to rank debt items by reach, impact, confidence, and effort.
  • Tracking & governance with a centralized registry to monitor debt trends and align work with sprints and risk management.
  • Real-world scenarios: legacy migrations, incremental refactors, and governance discussions to justify payoff.

Quick Start

Identify and prioritize debt in your codebase with a structured plan.

Frequently Asked Questions about tech-debt-management

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

FAQPage Schema
How do I prioritize technical debt in a legacy codebase?▼

Technical debt is classified into categories like design, code, test, documentation, dependency, and infrastructure debt. This taxonomy provides actionable detection cues to identify hidden code issues across software projects of any size.

What is the best way to track technical debt during refactoring sprints?▼

The best way to track technical debt is by using a centralized registry that monitors debt trends and aligns paydown work with refactoring sprints. This governance approach justifies payoff during incremental refactors and legacy migrations.

Can I use a RICE score to manage code health and dependency debt?▼

No specific dependencies or tooling components are required to start identifying and classifying technical debt. The workflow applies to software projects of any size, supporting scenarios from incremental refactors to legacy migrations without mandatory setup.

When should I not use a structured workflow for technical debt paydown?▼

A structured technical debt paydown workflow is not ideal for ad-hoc code fixes that lack governance needs or risk management alignment. It is designed for systematic debt tracking, legacy migrations, and justifying focused refactors to stakeholders.

Related Skills

Explore More Software Engineering Skills→
nikhillinitnikhillinit

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Community
Advanced
sahinsahin
1

tech-debt

Identify, classify, and prioritize technical debt items from engineering data sources.

Community
Advanced
HsnSaboorHsnSaboor

refactoring-expert

Refactors code using Martin Fowler's catalog and functional programming practices.

Community
Advanced
RangeyRoverRangeyRover
3

speckit.checker

Run static analysis across multiple languages and generate prioritized issue reports.

Community
Intermediate