technical-debt-management

Classify technical debt by quadrant and prioritize refactors for frequently modified services.

Updated Mar 26, 2026

Search Tags:#refactoring #code-quality #clean-code #technical-debt #stakeholder-communication #debt-prioritization

Ready to run

npx skills add https://github.com/johnnystefan/test-saas-business --skill technical-debt-management-johnnystefan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: technical-debt-management
Source: https://github.com/johnnystefan/test-saas-business/tree/main/skills/technical-debt-management
Command: npx skills add https://github.com/johnnystefan/test-saas-business --skill technical-debt-management-johnnystefan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides clarity on the hidden development costs caused by shortcuts so teams can communicate and address technical debt instead of letting it slow future work.

Core Features & Use Cases

Debt Detection: Identify high-interest areas by monitoring change velocity and surface risky modules that now take far longer to modify.
Quadrant Classification: Classify shortcuts as reckless or prudent, premeditated or inadvertent, to provide context on intent and urgency.
Prioritization Guidance: Recommend focusing refactors on frequently touched, complex code and explain the hours saved to stakeholders when advocating for cleanup.

Quick Start

Assess the recently modified module, classify its technical debt quadrant, and summarize the interest cost and refactor savings for stakeholders.

Frequently Asked Questions about technical-debt-management

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

FAQPage Schema

How do I prioritize technical debt across frequently modified services?▼

To prioritize technical debt, you assess recently modified modules to classify their debt quadrant, measure the interest cost of delayed refactoring, and calculate the hours saved to recommend actionable refactors for high-risk areas.

What is the best way to communicate technical debt impact to stakeholders?▼

Communicating technical debt impact to stakeholders requires summarizing the interest cost of shortcuts and explaining the hours saved through cleanup, which clarifies hidden development costs and justifies refactoring efforts.

How do I classify technical debt as reckless or prudent?▼

Classifying technical debt as reckless or prudent involves evaluating the quadrant origin of shortcuts to determine if they were premeditated or inadvertent, providing context on intent and urgency for prioritization.

How do I identify high-interest technical debt in my codebase?▼

Identifying high-interest technical debt involves monitoring change velocity to surface risky modules that now take far longer to modify, helping teams detect hidden development costs caused by shortcuts in frequently touched code.

When should I evaluate feature cost against existing technical debt?▼

You should evaluate feature cost against existing technical debt when reviewing refactors or assessing business pressure, ensuring that the interest level and prioritization criteria are factored into recommending actionable refactors.