skills.rest
ngochuy13
ngochuy13COMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Identify, categorize, and prioritize technical debt with impact, risk, and effort scoring.

Updated Apr 23, 2026
Search Tags:#code quality#architecture#refactoring#technical debt#prioritization#risk scoring#maintenance backlog
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill tech-debt-ngochuy13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/tech-debt
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill tech-debt-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tech debt planning helps teams stop accumulating hidden engineering costs by systematically identifying, categorizing, and prioritizing what to refactor or fix next.

Core Features & Use Cases

  • Debt categorization across code, architecture, tests, dependencies, documentation, and infrastructure.
  • Priority scoring that balances impact, risk, and effort to generate an ordered remediation backlog.
  • Phased remediation planning that fits alongside feature work rather than requiring a full stop.

Quick Start

Use the tech-debt skill to generate a prioritized list of technical debt items with estimated effort, business justification, and a phased remediation plan based on scoring.

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 when planning a refactoring backlog?▼

To prioritize technical debt, you score items by balancing business impact, risk, and inverted effort. This generates an ordered remediation backlog that justifies what to refactor first based on objective priority scoring.

What categories of technical debt should I track during a code health audit?▼

A technical debt audit should track debt across code, architecture, tests, dependencies, documentation, and infrastructure. Categorizing technical debt ensures you capture all hidden engineering costs systematically during maintenance triage.

Can I generate a maintenance backlog that fits alongside regular feature work?▼

Yes, you can generate a phased remediation plan that fits refactoring alongside feature work. This approach balances impact, risk, and effort to sequence maintenance tasks without requiring a full development stop.

What is the best way to score code quality risks for maintenance triage?▼

The best way to score code quality risks is by evaluating impact, risk, and inverted effort. This scoring mechanism produces a prioritized remediation list with justifications for maintenance backlog triage.

Related Skills

Explore More Software Engineering Skills→
ConsiliencyConsiliency
8

security-audit

Scan codebases for OWASP vulnerabilities and generate prioritized remediation reports.

Official
Intermediate
tarunccettarunccet
5

retro

Converts team feedback and sprint metrics into a markdown retro with prioritized action items.

Community
Intermediate
Tonybleything76Tonybleything76

Tech Debt Tracker

Scan codebases to identify, prioritize, and track technical debt.

Community
Advanced
xloxn69xloxn69
7

agileflow-sprint-planner

Generate a balanced Markdown sprint plan from backlog stories and team capacity.

Community
Intermediate