skills.rest
w95
w95COMMUNITY
Explore all skills by this author →
GitHub

tech-debt

Identify, categorize, and prioritize technical debt across code and infrastructure.

145|36|Updated Feb 26, 2026
Search Tags:#code quality#refactoring#maintenance#technical debt#tech debt#code health
One-click install
npx skills add https://github.com/w95/awesome-claude-corporate-skills --skill tech-debt-w95
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/w95/awesome-claude-corporate-skills/tree/main/08-it-engineering/tech-debt
Command: npx skills add https://github.com/w95/awesome-claude-corporate-skills --skill tech-debt-w95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams systematically identify, categorize, and prioritize technical debt to improve code quality and development velocity.

Core Features & Use Cases

  • Identification: Recognizes various types of technical debt including code, architecture, test, dependency, documentation, and infrastructure debt.
  • Categorization: Provides clear examples and associated risks for each debt category.
  • Prioritization: Employs a framework to score debt based on impact, risk, and effort, generating a prioritized list.
  • Remediation Planning: Outputs a phased plan for addressing technical debt alongside feature development.
  • Use Case: An engineering lead can use this skill to conduct a quarterly technical debt audit, presenting a clear, actionable plan to management.

Quick Start

Run a technical debt audit and provide a prioritized list of refactoring tasks.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I audit and prioritize technical debt across my codebase?▼

To prioritize technical debt, this Skill identifies and categorizes debt across code, architecture, testing, dependencies, and infrastructure. It scores each item based on impact, risk, and effort to generate a prioritized backlog for maintenance.

What is the best way to categorize technical debt for a management presentation?▼

Categorizing technical debt for management involves structuring items by type, such as code, architecture, test, dependency, and documentation debt. This Skill provides clear examples and associated risks for each category to support phased remediation planning.

How do you balance technical debt refactoring with feature development?▼

Balancing refactoring with feature development requires a phased remediation plan. This Skill outputs structured plans that schedule code health improvements alongside ongoing feature delivery to maintain development velocity.

Can I use this to assess architecture and infrastructure debt, not just code quality?▼

Yes, you can assess architecture and infrastructure debt along with code quality. This Skill explicitly identifies and evaluates technical debt across multiple domains, including architecture, testing, dependencies, documentation, and infrastructure.

How does a technical debt scoring framework work for maintenance backlog management?▼

A technical debt scoring framework evaluates items by impact, risk, and effort. This Skill employs this structured approach to assess maintenance backlogs, generating a prioritized list of refactoring tasks for engineering teams.

Related Skills

Explore More Software Engineering Skills→
travisjneumantravisjneuman
88

tech-debt-analyzer

Analyze codebases for technical debt using Python static analysis scripts.

Community
Intermediate
ericfisherdevericfisherdev
1

move-to-sprint

Move Jira issues to active, specific, or future sprints via Python script.

Community
Intermediate
SungmasterSungmaster

requesting-code-review

Dispatch a code reviewer subagent to evaluate changes against requirements.

Community
Intermediate
CassiiopeiaCassiiopeia
7

pro-refactor-analyze

Detect code smells and generate refactoring plans without modifying source code.

Community
Advanced