skills.rest
PoyoPoak
PoyoPoakCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Categorize and prioritize technical debt using Impact, Risk, and Effort scoring.

Updated Aug 23, 2026
Search Tags:#code quality#software engineering#refactoring#technical debt#prioritization#triage#architecture debt
One-click install
npx skills add https://github.com/PoyoPoak/FastAPI-App-Template --skill tech-debt-poyopoak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/PoyoPoak/FastAPI-App-Template/tree/main/.agents/skills/tech-debt
Command: npx skills add https://github.com/PoyoPoak/FastAPI-App-Template --skill tech-debt-poyopoak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify, categorize, and prioritize technical debt to help teams focus on high-impact refactors and improvements.

Core Features & Use Cases

  • Categorizes debt into code, architecture, tests, dependencies, documentation, and infrastructure.
  • Uses a scoring framework (Impact, Risk, Effort) to rank items and guide remediation.
  • Produces actionable roadmaps and phased backlogs for sprints and releases.
  • Real-world use: during a quarterly health check, generate a prioritized debt list and concrete next steps.

Quick Start

Summarize your codebase's current technical debt and generate a prioritized remediation 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 across a codebase for maintenance backlog grooming?▼

To prioritize technical debt during backlog grooming, you must categorize items across architecture, code, and tests, then apply a structured scoring framework based on Impact, Risk, and Effort to rank remediation tasks.

What is the best way to categorize architecture debt during a code health assessment?▼

The best way to categorize architecture debt during a code health assessment is to group items into distinct structural types such as code, architecture, tests, dependencies, documentation, and infrastructure for clear triage.

Can I generate a phased remediation roadmap from a prioritized technical debt list?▼

Yes, you can generate a phased remediation roadmap by taking the prioritized technical debt list, derived from the Impact, Risk, and Effort scoring framework, and feeding those actionable outputs directly into sprints and releases.

Does this technical debt triage framework require specific dependencies to run?▼

No, this technical debt triage framework requires no specific external dependencies to run, allowing software teams to independently conduct architectural reviews and maintenance backlog grooming during quarterly health checks.

How does a scoring framework help manage refactoring tasks for software engineering teams?▼

A scoring framework helps manage refactoring tasks by evaluating each technical debt item's Impact, Risk, and Effort, enabling software engineering teams to focus on high-impact improvements and produce concrete next steps.

When should I not use a structured framework for technical debt prioritization?▼

You should not use a structured framework for technical debt prioritization when dealing with isolated, trivial code fixes that require no architectural review, triage scoring, or integration into broader sprint roadmaps and release backlogs.

Related Skills

Explore More Software Engineering Skills→
li3pli3p

debt-scan

Identify and prioritize technical debt in a codebase for remediation planning.

Community
Intermediate
FoundationForgeFoundationForge

tech-debt

Identify, categorize, and prioritize technical debt across a codebase.

Official
Intermediate
rioX432rioX432
2

audit

Audit codebases for tech debt, quality, architecture, and dependency issues.

Community
Advanced
ilove323ilove323

tech-debt

Identify and prioritize technical debt using impact, risk, and effort scoring.

Community
Advanced