tech-debt

Name: tech-debt
Availability: InStock
Author: codephobiia

Identify and catalog technical debt with severity, location, category, and estimated fix costs across a codebase.

8|Updated Apr 16, 2026

Search Tags:#architecture #prioritization #refactor #code-quality #risk-management #tech-debt

Ready to run

npx skills add https://github.com/CodePhobiia/claude-roblox-game-studio --skill tech-debt-codephobiia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/CodePhobiia/claude-roblox-game-studio/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/CodePhobiia/claude-roblox-game-studio --skill tech-debt-codephobiia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and catalog technical debt across a codebase to guide periodic audits and remediation planning.

Core Features & Use Cases

Debt discovery and documentation across modules, files, and architectures.
Severity tagging, location mapping, and estimated fix costs to enable prioritization.
Use Case: Run a debt audit at sprint boundaries to decide next cleanup tasks and track progress over time.

Quick Start

Run the tech-debt catalog to enumerate debt items and generate a prioritized report.

Frequently Asked Questions about tech-debt

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

FAQPage Schema

How do I identify and catalog technical debt across my codebase?▼

To catalog technical debt, the Skill enumerates debt items across architectures, modules, and scripts, tagging each with severity, location, and category. This produces a structured inventory with prioritization data for scheduled remediation planning.

What is the best way to prioritize code refactor tasks during a sprint audit?▼

Prioritizing code refactor tasks requires estimated fix costs and severity tagging. The Skill generates a structured debt inventory with this data, enabling teams to decide what to clean up next and track progress over time at sprint boundaries.

When should I run a tech debt audit on my software architecture?▼

You should run a tech debt audit at sprint boundaries or when deciding what to clean up next across your software architecture. Periodic debt audits help track progress over time and generate prioritized reports for scheduled remediation planning.

Can I estimate fix costs for code quality issues across different modules?▼

Yes, you can estimate fix costs for code quality issues across different modules. The Skill maps the location of debt items and applies severity tagging with estimated fix costs to enable accurate prioritization and scheduled remediation planning.

Does this tech debt analysis tool work with scripts and broad architectures?▼

Yes, the tech debt analysis works with scripts and broad architectures. It discovers and documents debt across modules, files, and architectures, applying severity tags and estimated fix costs to produce a structured debt inventory for remediation planning.

Why do I need a structured debt inventory for risk management and refactoring?▼

You need a structured debt inventory for risk management because it provides prioritization data, severity tagging, and estimated fix costs. This enables scheduled remediation planning and helps decide what to clean up next across your codebase.