skills.rest
JeremyDev87
JeremyDev87COMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt

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

31|3|Updated Dec 12, 2025
Search Tags:#code quality#planning#architecture#refactoring#technical debt#prioritization#roi
One-click install
npx skills add https://github.com/JeremyDev87/codingbuddy --skill tech-debt-jeremydev87
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/JeremyDev87/codingbuddy/tree/main/packages/rules/.ai-rules/skills/tech-debt
Command: npx skills add https://github.com/JeremyDev87/codingbuddy --skill tech-debt-jeremydev87

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical debt is the compounding drag on delivery, architecture, and maintainability when not managed, leading to slower feature work and higher risk.

Core Features & Use Cases

  • Automated discovery and assessment of debt types (architectural, code quality, test debt) to surface where effort is needed.
  • ROI-based prioritization and paydown planning with phased, actionable steps that align with product cadence.
  • Debt governance artifacts (tech debt register, paydown plans) to guide sprint goals and long-term health.

Quick Start

Run a structured debt assessment and generate an ROI-based 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 refactoring during sprint planning?▼

Prioritize technical debt by running a structured assessment to quantify impact and using ROI-based prioritization to generate phased, actionable paydown plans that align with your product delivery cadence.

What is the best way to assess and quantify technical debt impact?▼

Assess technical debt through automated discovery of architectural, code quality, and test debt types, surfacing where effort is needed and quantifying the compounding drag on delivery and maintainability.

How do I create a technical debt paydown plan that aligns with feature delivery?▼

Create a technical debt paydown plan by generating ROI-based, phased actionable steps that balance debt resolution with product cadence, ensuring incremental paydown guidance that fits sprint goals.

Can I use this for architecture reviews and quarterly health checks?▼

Yes, you can use structured debt assessment during architecture reviews and quarterly health checks to quantify debt impact, generate governance artifacts, and plan incremental paydown for long-term health.

What governance artifacts are needed to manage technical debt effectively?▼

Manage technical debt effectively using governance artifacts like a tech debt register and ROI-based paydown plans, which guide sprint goals and track long-term architectural health and maintainability.

Related Skills

Explore More Software Engineering Skills→
0xRayAI0xRayAI

code-analyzer

Analyze source code metrics, patterns, and dependency graphs.

Official
Advanced
masharrattmasharratt
14

google-sheets-sprint-order

Compute dependency-aware execution plans for Google Sheets sprint pipelines.

Community
Advanced
onmaxonmax

request-refactor-plan

Plan code refactoring into tiny, atomic commits with test coverage assessment.

Community
Intermediate
htafollahtafolla
5

refactoring-strategies

Provide code refactoring techniques and technical debt reduction strategies.

Community
Basic