managing-tech-debt

Identify and quantify technical debt across code and architecture.

Updated Mar 15, 2026

Search Tags:#refactoring #product management #tech debt #legacy code #roadmapping #stakeholders

Ready to run

npx skills add https://github.com/cvillamarp-lgtm/skillspodcast --skill managing-tech-debt-cvillamarp-lgtm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: managing-tech-debt
Source: https://github.com/cvillamarp-lgtm/skillspodcast/tree/main/skills/managing-tech-debt
Command: npx skills add https://github.com/cvillamarp-lgtm/skillspodcast --skill managing-tech-debt-cvillamarp-lgtm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps product and engineering teams identify, quantify, and address technical debt to improve delivery speed, system health, and long-term sustainability.

Core Features & Use Cases

Debt assessment: catalog current debt across code, architecture, and processes to understand scope.
Prioritization & roadmapping: align debt payoff with business goals and release plans.
Stakeholder governance: build a business case for refactoring, maintenance, and debt reduction with leadership.

Quick Start

Identify the top 5 debt items and draft a 90-day plan to address them.

Frequently Asked Questions about managing-tech-debt

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

FAQPage Schema

How do I quantify technical debt to improve product delivery velocity?▼

Quantify technical debt by cataloging current issues across legacy code, architecture, and processes to understand scope and establish clear metrics. This assessment identifies specific bottlenecks to improve delivery speed and system stability.

What is the best way to integrate tech debt refactoring into a product roadmap?▼

Integrate tech debt refactoring by aligning debt payoff tasks with business goals and release plans. You can draft a 90-day plan to address top prioritized debt items alongside new product features.

How do I get stakeholder buy-in for legacy code maintenance and rewrites?▼

Get stakeholder buy-in by building a business case for refactoring that demonstrates how reducing technical debt improves delivery speed and system health. Clear metrics and ownership help leadership understand the trade-offs.

When should I choose an incremental fix over a complete rewrite for architectural debt?▼

Choose incremental fixes over rewrites when you need to maintain delivery stability while addressing architectural debt. Evaluate trade-off decisions based on clear metrics and the impact on long-term system sustainability.

Can I use this approach for managing technical debt across legacy code and processes?▼

Yes, this approach applies to managing technical debt across legacy code, architectural debt, and internal processes. It helps establish ownership and integrate debt reduction work directly into product roadmaps.