skills.rest
jforksy
jforksyCOMMUNITY
Explore all skills by this author →
𝕏@jeff_forkanGitHub

tech-debt

Identify, classify, and plan technical debt paydown from engineering data files.

Updated Aug 27, 2026
Search Tags:#planning#sprint planning#tech debt#classify#prioritize#Fowler quadrant#identify
One-click install
npx skills add https://github.com/jforksy/claude-skills --skill tech-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/jforksy/claude-skills/tree/main/tech-debt
Command: npx skills add https://github.com/jforksy/claude-skills --skill tech-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams identify, classify, prioritize, and plan technical debt paydown, enabling deliberate improvement of code quality and delivery speed.

Core Features & Use Cases

  • Surface debt items from code reviews, incident post-mortems, and developer friction points.
  • Classify using the Fowler Quadrant and impact-based prioritization to create actionable paydown plans.
  • Generate sprint-ready debt backlogs and roadmaps that balance risk, effort, and business value.

Quick Start

To begin, load your current debt data, run the assessment, and review the generated backlog and paydown plan.

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 for sprint planning?▼

Prioritize technical debt by classifying items using the Fowler Quadrant and evaluating impact to generate a sprint-ready, risk-balanced paydown plan. This approach balances business value, risk, and effort for engineering teams.

What is the Fowler Quadrant for classifying technical debt?▼

The Fowler Quadrant is a classification model used to categorize technical debt items based on their characteristics. Applying this model helps engineering teams deliberately improve code quality by creating actionable paydown plans.

How do I create a technical debt paydown plan from code reviews and incidents?▼

Create a technical debt paydown plan by surfacing debt items from code reviews and incident post-mortems, then loading the data to generate a prioritized debt registry and actionable development roadmap.

What data do I need to generate a technical debt registry and paydown plan?▼

Generating a technical debt registry requires loading JSON data from engineering tech debt, tech stack, engineering scorecard, and CFO latest forecast files to align paydown plans with business forecasts.

Can I balance technical debt paydown with ongoing development work?▼

Yes, you can balance technical debt paydown with ongoing development by generating a sprint-ready debt backlog. This backlog prioritizes items by risk, effort, and business value to ensure deliberate code quality improvement.

When should engineering teams systematically pay down technical debt?▼

Engineering teams should systematically pay down technical debt during ongoing development and sprint planning to improve delivery speed. Surfacing developer friction points and incident post-mortems helps identify and prioritize necessary debt paydown.

Related Skills

Explore More Software Engineering Skills→
sahinsahin
1

tech-debt

Identify, classify, and prioritize technical debt items from engineering data sources.

Community
Advanced
JeremyDev87JeremyDev87
31

tech-debt

Identify, prioritize, and plan technical debt resolution with ROI-based paydown steps.

Community
Advanced
ailabs-393ailabs-393
438

tech-debt-analyzer

Identify and quantify technical debt across multi-language codebases.

Community
Intermediate
sandalsoftsandalsoft

technical-debt-manager

Inventory technical debt across code quality, tests, and dependencies.

Community
Advanced