tech-debt

Name: tech-debt
Availability: InStock
Author: sun2443

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

Updated Apr 8, 2026

Search Tags:#architecture #refactoring #technical debt #prioritization #code health #remediation planning #maintenance backlog

Ready to run

npx skills add https://github.com/sun2443/designer-skills --skill tech-debt-sun2443

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/sun2443/designer-skills/tree/main/engineering/skills/tech-debt
Command: npx skills add https://github.com/sun2443/designer-skills --skill tech-debt-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify technical debt that quietly slows delivery, increases defect rates, and raises maintenance effort.

Core Features & Use Cases

Debt categorization: Organizes debt into code, architecture, test, dependency, documentation, and infrastructure types with concrete examples.
Prioritization framework: Scores each item by impact, risk, and effort to produce a rational fix order.
Actionable remediation planning: Produces a phased plan that can be executed alongside feature work, with business justification.

Quick Start

Trigger the skill by asking: "tech debt audit for our repo and prioritize the top refactors with a phased remediation plan."

Frequently Asked Questions about tech-debt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What types of technical debt should I look for during a code health audit?▼

Technical debt is categorized into code, architecture, test, dependency, documentation, and infrastructure types. This categorization provides concrete examples to help teams identify specific weaknesses across the entire codebase.

What is the best way to categorize architecture weaknesses in a maintenance backlog?▼

Yes, you can generate a phased remediation plan designed to execute alongside feature work. It includes business justifications for each item, ensuring maintenance backlogs are addressed without halting delivery.

How do I prioritize technical debt items for refactoring?▼

The best way to categorize architecture weaknesses is by grouping them into distinct technical debt types. This approach applies to maintenance backlogs and code quality reviews, turning vague weaknesses into actionable, scored items.

Can I generate a phased remediation plan alongside feature work?▼

Estimating effort for technical debt involves scoring each item using an inverted effort model alongside impact and risk. This scoring requirement outputs a prioritized list with precise effort estimates for remediation planning.

Does technical debt prioritization work for both code and infrastructure weaknesses?▼

Yes, technical debt prioritization works for both code and infrastructure weaknesses. The framework evaluates maintenance backlogs across code, architecture, tests, dependencies, documentation, and infrastructure to guide refactoring decisions.