skills.rest
pgm1980
pgm1980COMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Prioritize technical debt by scoring impact, risk, and effort.

Updated Apr 29, 2026
Search Tags:#code quality#refactoring#technical debt#prioritization#risk assessment#remediation planning#maintenance backlog
One-click install
npx skills add https://github.com/pgm1980/stryker-netx --skill tech-debt-pgm1980
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/pgm1980/stryker-netx/tree/main/.claude/skills/tech-dept
Command: npx skills add https://github.com/pgm1980/stryker-netx --skill tech-debt-pgm1980

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tech-debt work often feels subjective, untracked, and hard to sequence, causing teams to defer important fixes until they become major outages or costly slowdowns.

Core Features & Use Cases

  • Debt identification by type: organizes issues into code, architecture, test, dependency, documentation, and infrastructure categories with concrete examples.
  • Consistent prioritization: scores each item using Impact, Risk, and Effort to compute a repeatable Priority formula.
  • Actionable outputs: produces a prioritized list with effort estimates, business justification, and a phased remediation plan that can run alongside feature delivery.

Quick Start

Trigger an analysis by asking the AI for a “technical debt audit” and include the areas you want reviewed, such as refactoring candidates, code health concerns, or items in your maintenance backlog.

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 in my maintenance backlog?▼

Prioritize technical debt by scoring each item using the formula (Impact + Risk) x (6 - Effort) to generate a repeatable priority ranking. This method turns subjective code smells into a measurable sequence for remediation planning.

What categories should I include in a technical debt audit?▼

A technical debt audit should include categories for code, architecture, tests, dependencies, documentation, and infrastructure. Organizing issues into these areas provides concrete examples for structured remediation planning.

How do I plan refactoring work alongside feature delivery?▼

Plan refactoring alongside feature delivery by generating a phased remediation plan that includes effort estimates and business justification for each prioritized item. This sequences maintenance tasks without blocking feature development.

What is the best way to assess risk for codebase refactoring candidates?▼

Assess risk for refactoring candidates by applying a consistent scoring formula that weighs impact, risk, and effort. This generates an actionable list with business justifications to determine what to fix first.

Can I use this technical debt scoring for infrastructure and dependency upgrades?▼

Yes, technical debt scoring applies to infrastructure and dependency upgrades alongside code, architecture, tests, and documentation. The prioritization formula evaluates these maintenance items based on measurable impact and effort.

Related Skills

Explore More Product & Management Skills→
foutoucourfoutoucour

technical-debt-radar

Identify and quantify technical debt with remediation effort estimates and risk scores.

Community
Advanced
yalehyaleh
21

Technical Debt Management

Quantify and prioritize technical debt using the SQALE methodology.

Community
Advanced
kiryteokiryteo
1

tech-debt

Identify, categorize, and prioritize technical debt across code, architecture, tests, dependencies, documentation, and infrastructure.

Community
Intermediate
sun2443sun2443

tech-debt

Categorize and prioritize technical debt with impact, risk, and effort scores.

Community
Intermediate