skills.rest
kiryteo
kiryteoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt

Identify, categorize, and prioritize technical debt across code, architecture, tests, dependencies, documentation, and infrastructure.

1|Updated Mar 9, 2026
Search Tags:#refactoring#prioritization#risk#tech-debt#technical-debt#code-maintenance
One-click install
npx skills add https://github.com/kiryteo/opencode-setup --skill tech-debt-kiryteo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/kiryteo/opencode-setup/tree/main/skills/tech-debt
Command: npx skills add https://github.com/kiryteo/opencode-setup --skill tech-debt-kiryteo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify, categorize, and prioritize technical debt to reduce maintenance risk and speed delivery.

Core Features & Use Cases

  • Identify debt types (code, architecture, tests, dependencies, documentation, infrastructure) and assess their impact.
  • Prioritize work using the defined scoring formula and generate a phased remediation plan.
  • Apply the framework across projects to align engineering efforts with business priorities.

Quick Start

Run a debt audit on your codebase by listing current debts and scoring them with the prioritization framework.

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 items using Impact, Risk, and Effort. This framework evaluates code, architecture, and infrastructure debt to generate a phased remediation plan aligned with business priorities.

What are the different types of technical debt I should track in my codebase?▼

Technical debt types include code, architecture, tests, dependencies, documentation, and infrastructure debt. Tracking these categories helps assess maintenance risk and guides refactoring efforts to accelerate delivery.

How do I create a phased remediation plan for technical debt?▼

Create a phased remediation plan by listing current debts and scoring them with the prioritization formula. This approach structures refactoring work into manageable phases to reduce maintenance risk and improve release readiness.

Can I use this technical debt framework across multiple projects?▼

Yes, you can apply this framework across projects to align engineering efforts with business priorities. It standardizes how technical debt is identified, categorized, and prioritized to accelerate delivery consistently.

What's the best way to assess technical debt impact on delivery speed?▼

Assess technical debt impact by auditing your codebase and evaluating debt types against the prioritization formula. This identifies maintenance risks and guides refactoring to accelerate delivery and ensure release readiness.

When should I prioritize technical debt over new feature development?▼

Prioritize technical debt when maintenance risk threatens delivery speed or release readiness. Using the Impact, Risk, and Effort formula identifies high-priority refactoring tasks that align engineering efforts with business priorities.

Related Skills

Explore More Software Engineering Skills→
sun2443sun2443

tech-debt

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

Community
Intermediate
vobbilisvobbilis
1

code-refactoring

Automate code refactoring with import tracking and a four-phase workflow.

Community
Advanced
AZANIRAZANIR
2

qa-risk-analyzer

Rank testing effort by complexity, change frequency, and test coverage.

Community
Advanced
adrianliechtiadrianliechti
4

tech-debt

Identify, categorize, and prioritize technical debt across codebases and systems.

Community
Intermediate