managing-tech-debt

Prioritize technical debt and generate incremental refactoring plans.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Andy-HNU/AndyClaw --skill managing-tech-debt-andy-hnu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-tech-debt
Source: https://github.com/Andy-HNU/AndyClaw/tree/main/skills/lenny-managing-tech-debt
Command: npx skills add https://github.com/Andy-HNU/AndyClaw --skill managing-tech-debt-andy-hnu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Help teams align on when to pay down technical debt, decide between rewrites and incremental fixes, and articulate a compelling business case to stakeholders.

Core Features & Use Cases

  • Structured guidance for diagnosing debt, prioritizing interventions, and building a business case.
  • Practical framework drawn from 18 industry voices to justify decisions and avoid unnecessary rewrites.
  • Use Case: When facing legacy code or maintenance pain, generate a prioritized plan balancing new features and debt reduction.
  • Deep Dive: See references/guest-insights.md for full insights from 18 guests to inform decisions.

Quick Start

Summarize your current tech debt and generate a prioritized, incremental refactoring plan.

Frequently Asked Questions about managing-tech-debt

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

FAQPage Schema
How do I build a business case for technical debt reduction to secure leadership buy-in?

To build a business case for technical debt, articulate a structured framework that aligns debt reduction with new feature delivery. This approach justifies refactoring decisions to stakeholders by demonstrating evidence-based prioritization and balancing maintenance pain with product goals.

What is the best way to prioritize technical debt interventions in legacy code?

Prioritizing technical debt in legacy code requires structured guidance to diagnose debt severity and generate a prioritized, incremental refactoring plan. This method balances incremental fixes against new feature work rather than defaulting to complete rewrites.

How do I balance paying down technical debt with shipping new product features?

Balancing technical debt with new features involves generating a prioritized plan that weighs maintenance pain against product management goals. It provides a structured framework to decide when to schedule incremental improvements without halting feature delivery.

Should I rewrite legacy code or use incremental refactoring to manage tech debt?

Choosing between rewriting legacy code and incremental refactoring depends on structured guidance drawn from industry insights. The framework helps avoid unnecessary rewrites by evaluating maintenance pain and prioritizing targeted interventions based on evidence.

Does this tech debt management framework apply to small teams or only large product management organizations?

This technical debt management framework applies across legacy code environments and various team scales. It provides structured guidance for diagnosing debt and building a business case, helping any team align on prioritized incremental improvements and refactoring decisions.