skills.rest
lilbom32
lilbom32COMMUNITY
Explore all skills by this author →
GitHub

tech-debt

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

Updated Mar 15, 2026
Search Tags:#code quality#architecture#refactoring#technical debt#prioritization#risk-management#tech-debt
One-click install
npx skills add https://github.com/lilbom32/ketnoitrithuc --skill tech-debt-lilbom32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/lilbom32/ketnoitrithuc/tree/main/.claude/skills/engineering/1.1.0/skills/tech-debt
Command: npx skills add https://github.com/lilbom32/ketnoitrithuc --skill tech-debt-lilbom32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically identify, categorize, and prioritize technical debt to reduce maintenance burden and accelerate delivery.

Core Features & Use Cases

  • Debt categorization: classify issues into code, architecture, test, dependency, and infrastructure debt.
  • Prioritization framework: score impact, risk, and effort to generate a remediation backlog.
  • Phased remediation planning: produce a pragmatic plan aligned with feature work and timelines.

Quick Start

Identify and categorize your current technical debt across the codebase and architecture, then 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 for refactoring?▼

Prioritize technical debt by scoring impact, risk, and effort across code, architecture, tests, and dependencies. This structured framework generates a remediation backlog aligned with feature work and delivery timelines.

What types of technical debt should I categorize in my codebase?▼

Categorize technical debt into code, architecture, test, dependency, and infrastructure debt. Classifying issues across these domains systematically reduces maintenance burden and accelerates software delivery.

What is the best way to plan refactoring without stopping feature delivery?▼

The best way to plan refactoring alongside features is phased remediation planning. It produces a pragmatic plan that scores debt by impact and effort, integrating seamlessly into existing software timelines.

Can I use a technical debt framework for risk management and maintenance backlogs?▼

Yes, you can apply this framework to risk management and maintenance backlogs. It identifies and scores technical debt by impact and risk, generating a prioritized plan to improve code health efficiently.

Does technical debt prioritization work for both code quality and architecture issues?▼

Yes, technical debt prioritization works for both code quality and architecture issues. It systematically categorizes and scores debt across code, architecture, tests, and dependencies to produce a comprehensive remediation plan.

Related Skills

Explore More Software Engineering Skills→
lasswelltlasswellt
1

codebase-map

Analyze a codebase across technology, architecture, quality, and concerns to generate CODEBASE-MAP.md.

Community
Advanced
proffesor-for-testingproffesor-for-testing
436

risk-based-testing

Prioritize testing effort by risk with probability and impact scoring.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
0xmythril0xmythril
9

clawdtm-advisor

Locate, assess security risks, and install community OpenClaw skills.

Community
Basic