skills.rest
chavangorakh1999
chavangorakh1999COMMUNITY
Explore all skills by this author →
Website𝕏@grc_jrGitHub

tech-debt

Classify and prioritize technical debt using Fowler's matrix and impact, churn, and fix cost scores.

1|Updated Mar 6, 2026
Search Tags:#code quality#refactoring#prioritization#software architecture#developer productivity#tech debt
One-click install
npx skills add https://github.com/chavangorakh1999/sde-skills --skill tech-debt-chavangorakh1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-architecture/skills/tech-debt
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill tech-debt-chavangorakh1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams identify, classify, and prioritize technical debt, ensuring that debt is managed proactively rather than accumulating and hindering development velocity.

Core Features & Use Cases

  • Debt Classification: Categorize technical debt using Fowler's matrix (reckless, deliberate, inadvertent, prudent).
  • Prioritization: Score debt items based on impact, churn, and fix cost to determine payoff order.
  • Payoff Analysis: Calculate the ROI for addressing specific debt items.
  • Tracking Strategy: Implement a system for ongoing debt management.
  • Use Case: A team is struggling with slow development cycles due to legacy code. This Skill can help them analyze the existing debt, quantify its impact, and create a plan to systematically pay it down.

Quick Start

Use the tech-debt skill to analyze the technical debt in the UserService.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I prioritize technical debt items to improve developer productivity?▼

Classify technical debt using Fowler's matrix to categorize issues as reckless, deliberate, inadvertent, or prudent. This classification helps teams understand the nature and origin of accumulated code quality issues.

What is the best way to track and manage technical debt proactively?▼

The best way to manage technical debt proactively is to implement an ongoing tracking strategy that systematically quantifies the impact of legacy code. This prevents debt from accumulating and hindering development velocity.

How do I calculate the ROI for refactoring legacy code?▼

Calculate refactoring ROI by analyzing the payoff of addressing specific debt items against their fix cost and impact. This payoff analysis quantifies the value of improving software architecture and code quality.

Can I analyze technical debt for a specific service like UserService?▼

Yes, you can analyze technical debt for specific components like UserService. The skill evaluates targeted software architecture issues to quantify their impact and create a systematic plan to pay down the debt.

Related Skills

Explore More Software Engineering Skills→
Harshal1841AHarshal1841A

tech-debt-tracker

Detect, analyze, and track technical debt across codebases.

Community
Intermediate
runchr-comrunchr-com

retro

Facilitate structured sprint retrospectives and generate prioritized action items.

Official
Intermediate
dhruvinrsonidhruvinrsoni

tech-debt-tracking

Identify, categorize, score, and prioritize technical debt in software projects.

Community
Advanced
nikhillinitnikhillinit

tech-debt-tracker

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

Community
Advanced