skills.rest
paulanunes85
paulanunes85COMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt

Categorize technical debt and generate prioritized remediation plans with effort estimates.

Updated Aug 27, 2026
Search Tags:#refactoring#maintenance#prioritization#risk-assessment#technical-debt#code-health
One-click install
npx skills add https://github.com/paulanunes85/awesome-paulasilvatech-copilots --skill tech-debt-paulanunes85
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/paulanunes85/awesome-paulasilvatech-copilots/tree/main/plugins/engineering/skills/tech-debt
Command: npx skills add https://github.com/paulanunes85/awesome-paulasilvatech-copilots --skill tech-debt-paulanunes85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams uncover hidden technical debt, understand its impact, and prioritize remediation to improve code health and delivery speed.

Core Features & Use Cases

  • Debt Identification: Categorizes code, architecture, test, dependency, documentation, and infrastructure debt.
  • Prioritization Framework: Scores items by impact, risk, and effort to generate a clear remediation order.
  • Actionable Output: Produces a prioritized list with effort estimates, business justification, and a phased remediation plan.
  • Use Case: During sprint planning, a team can run this Skill to surface the most critical debt items that should be addressed alongside feature work.

Quick Start

Ask the skill to produce a prioritized technical debt report for the current codebase.

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

To prioritize technical debt, this Skill scores codebase, architecture, and infrastructure debt items by impact, risk, and effort to generate a ranked remediation list with business justifications and phased plans.

What types of technical debt can be identified and categorized in a codebase?▼

Technical debt identification categorizes issues across codebases, architectures, tests, dependencies, documentation, and infrastructure to uncover hidden issues and understand their impact on delivery speed.

How do I create a phased remediation plan for maintenance and code health issues?▼

You create a phased remediation plan by categorizing technical debt and scoring items by impact, risk, and effort, which produces actionable output with effort estimates and business justification for each item.

Can I estimate the effort required to fix dependency and infrastructure debt?▼

Yes, the prioritization framework scores dependency and infrastructure debt items by effort alongside impact and risk, generating a clear remediation order with specific effort estimates for each item.

What is the best way to assess technical debt risk before starting a refactoring project?▼

The best way to assess technical debt risk is to apply a prioritization framework that scores debt items by impact, risk, and effort, producing a prioritized report with business justification and a phased remediation plan.

Related Skills

Explore More Software Engineering Skills→
CarlosQ96CarlosQ96

tech-debt

Scan codebases for debt indicators and generate a prioritized risk register.

Community
Advanced
ydnikolaevydnikolaev
8

project-bro

Analyze software project state from docs and architecture files.

Community
Basic
Harshal1841AHarshal1841A

tech-debt-tracker

Detect, analyze, and track technical debt across codebases.

Community
Intermediate
CarGDevCarGDev

Code Auditor

Audit code quality by detecting dead code, complexity, duplication, and architectural smells.

Community
Intermediate