skills.rest
cy-wali
cy-waliCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Identify and prioritize technical debt with a scoring framework and remediation plan.

1|Updated Mar 19, 2026
Search Tags:#refactoring#technical debt#prioritization#risk assessment#tech debt#code health#maintenance backlog
One-click install
npx skills add https://github.com/cy-wali/knowledge --skill tech-debt-cy-wali
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/cy-wali/knowledge/tree/main/engineering/skills/tech-debt
Command: npx skills add https://github.com/cy-wali/knowledge --skill tech-debt-cy-wali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and prioritize technical debt to accelerate software delivery.

Core Features & Use Cases

  • Categorizes debt types across code, architecture, tests, dependencies, and docs.
  • Provides a scoring framework (Impact, Risk, Effort) and a generated remediation plan.
  • Real-world use: prioritize refactoring, dependency updates, and test suite improvements to reduce maintenance overhead.

Quick Start

Run a tech debt audit to categorize every debt item 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 and architecture?▼

Technical debt prioritization uses a scoring framework evaluating Impact, Risk, and Effort to categorize debt items across code, architecture, tests, and dependencies, generating a phased remediation plan to accelerate software delivery.

What is the best way to categorize a maintenance backlog for refactoring?▼

Categorizing a maintenance backlog involves auditing code health to classify debt types across code, architecture, tests, dependencies, and docs, resulting in a structured debt inventory that guides actionable remediation efforts.

Can I generate a remediation plan for dependency updates and test suite improvements?▼

Yes, you can generate a remediation plan for dependency updates and test suite improvements by running a tech debt audit that scores maintenance backlog items and outputs a phased remediation strategy to reduce overhead.

How does risk assessment work when prioritizing code health refactoring tasks?▼

Risk assessment for code health refactoring works by scoring each technical debt item using a structured framework that weighs Impact, Risk, and Effort, prioritizing high-risk maintenance backlog items for immediate remediation.

When do I need a structured debt inventory for software engineering maintenance?▼

You need a structured debt inventory for software engineering maintenance when accumulation of technical debt across code, architecture, and dependencies slows software delivery, requiring prioritized refactoring to reduce maintenance overhead.

Related Skills

Explore More Software Engineering Skills→
ToowireddToowiredd
33

repository-analyzer

Analyze repository structure, languages, frameworks, and technical debt into Markdown documentation.

Community
Advanced
rakibulismrakibulism
2

tech-debt

Categorize technical debt and score impact, risk, and effort for remediation planning.

Community
Intermediate
foutoucourfoutoucour

technical-debt-radar

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

Community
Advanced
wichan7wichan7

tech-debt-tracker

Scans codebases to identify, categorize, and prioritize technical debt.

Community
Advanced