tech-debt

Identify, categorize, and prioritize technical debt across codebases.

3|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/ruskicoder/system-prompts --skill tech-debt-ruskicoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/ruskicoder/system-prompts/tree/main/prompt-orchestrator/.opencode/skills/tech-debt
Command: npx skills add https://github.com/ruskicoder/system-prompts --skill tech-debt-ruskicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams accumulate technical debt without a clear way to measure or rank it, making it hard to decide what to refactor first. This Skill provides a structured framework to audit debt, score it, and turn it into an actionable remediation plan. ## Core Features & Use Cases - Debt Categorization: Classifies issues into six types: code, architecture, test, dependency, documentation, and infrastructure debt. - Prioritization Scoring: Ranks items using a formula based on impact, risk, and effort so the highest-value fixes surface first. - Phased Remediation Plan: Produces a prioritized backlog with effort estimates and business justification that fits alongside feature work. - Use Case: Ask for a technical debt audit of a legacy service and receive a scored list of refactoring priorities, such as replacing an unmaintained dependency or splitting a monolith, with justification for each item. ## Quick Start Ask the AI to perform a technical debt audit of your repository and produce a prioritized refactoring 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 in my codebase?▼

Score each debt item on impact (1-5), risk (1-5), and effort (1-5), then compute priority as (Impact + Risk) x (6 - Effort). This surfaces high-impact, low-effort fixes first and produces a ranked remediation list.

What types of technical debt should an audit cover?▼

A thorough audit covers six categories: code debt, architecture debt, test debt, dependency debt, documentation debt, and infrastructure debt. Each type carries distinct risks, from security vulnerabilities in outdated dependencies to scaling limits in monolithic architectures.

How do I justify refactoring work to stakeholders?▼

Attach a business justification to each prioritized item, explaining the cost of inaction such as slower development, regressions, or incident risk. Presenting debt as a scored, phased plan makes it easier to schedule alongside feature work.

When should a technical debt audit not be the priority?▼

If the codebase is being deprecated or rewritten soon, deep debt remediation has little return. Focus audits on actively maintained systems where debt directly slows delivery or increases incident risk.