What is the Fowler Tech Debt Matrix?

It is a framework that classifies technical debt into four quadrants—Reckless vs. Prudent and Deliberate vs. Inadvertent—to help teams understand the risk and origin of their code debt.

How is the priority score calculated?

The skill uses the formula: (Impact × Churn Rate) / Fix Cost. A higher score identifies 'quick wins' or high-pain areas that should be addressed immediately.

How does this skill help with sprint planning?

It recommends the 20% rule, where 20% of sprint capacity is allocated to debt payoff, ensuring the team stays fast and motivated without needing a 'big rewrite' quarter.

Can this skill generate business justifications for refactoring?

Yes, it includes a Payoff Analysis section that calculates the annual cost of debt in engineering time and potential revenue impact, making it easier to communicate with management.

Technical Debt Manager

Name: Technical Debt Manager
Author: chavangorakh1999

bychavangorakh1999

0•

Productividad y Flujo de Trabajo

Classifies and prioritizes technical debt using the Fowler matrix and ROI analysis to optimize engineering velocity.

The Technical Debt Manager skill provides a structured framework for engineering teams to move from subjective complaints about code quality to data-driven debt management. It utilizes the Fowler Tech Debt Matrix to categorize shortcuts as prudent or reckless, calculates priority scores based on impact and churn rate, and generates detailed payoff analyses. Whether you are planning a sprint or justifying a major refactor to stakeholders, this skill helps Claude provide clear, actionable recommendations for maintaining a healthy codebase without sacrificing product momentum.

Características Principales

01Structured technical debt register and tracking strategy

02Sprint capacity planning using the 20% debt-payoff rule

030 GitHub stars

04Fowler Tech Debt Matrix classification (Reckless/Prudent/Deliberate/Inadvertent)

05Quantitative priority scoring based on impact, churn, and fix cost

06Detailed payoff and ROI analysis for refactoring tasks

Casos de Uso

01Justifying technical maintenance work to non-technical stakeholders with business-impact data

02Prioritizing refactoring tasks during sprint planning based on engineering ROI

03Auditing legacy components to identify high-risk 'reckless' debt

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add chavangorakh1999/sde-skills tech-debt

For use in Claude.ai and ChatGPT

Características Principales

01Structured technical debt register and tracking strategy

02Sprint capacity planning using the 20% debt-payoff rule

030 GitHub stars

04Fowler Tech Debt Matrix classification (Reckless/Prudent/Deliberate/Inadvertent)

05Quantitative priority scoring based on impact, churn, and fix cost

06Detailed payoff and ROI analysis for refactoring tasks

Casos de Uso

01Justifying technical maintenance work to non-technical stakeholders with business-impact data

02Prioritizing refactoring tasks during sprint planning based on engineering ROI

03Auditing legacy components to identify high-risk 'reckless' debt

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add chavangorakh1999/sde-skills tech-debt

For use in Claude.ai and ChatGPT