skills.rest
openyak
openyakOFFICIAL
Explore all skills by this author →
GitHub

tech-debt

Identify and prioritize technical debt across codebases using Impact, Risk, and Effort scoring.

704|58|Updated Mar 20, 2026
Search Tags:#architecture#refactoring#prioritization#code-quality#risk-assessment#tech-debt#technical-debt
One-click install
npx skills add https://github.com/openyak/desktop --skill tech-debt-openyak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/openyak/desktop/tree/main/backend/app/data/plugins/engineering/skills/tech-debt
Command: npx skills add https://github.com/openyak/desktop --skill tech-debt-openyak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify, categorize, and prioritize technical debt to improve code quality and delivery velocity.

Core Features & Use Cases

  • Classify debt by type: code, architecture, test, dependency, documentation, and infrastructure.
  • Score and surface remediation priorities with a clear, actionable plan.
  • Use across monorepos, multi-repo ecosystems, and legacy systems to align engineering effort.

Quick Start

Run a quick debt audit over your codebase to surface top-priority refactors.

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 across multiple projects?▼

To prioritize technical debt across multiple projects, assess each item using Impact, Risk, and Effort scores. Calculate remediation priority using the formula Priority = (Impact + Risk) x (6 - Effort) to generate a clear, actionable refactoring plan.

How do I run a quick technical debt audit on my codebase?▼

Run a quick technical debt audit by evaluating your codebase against a scoring rubric. This surfaces top-priority refactors by categorizing debt into code, architecture, test, dependency, documentation, and infrastructure classes, then scoring them by Impact, Risk, and Effort.

What types of technical debt can I categorize and score?▼

You can categorize technical debt into six types: code, architecture, test, dependency, documentation, and infrastructure. Scoring these categories by Impact, Risk, and Effort helps surface remediation priorities to improve code quality and delivery velocity.

What is the best way to calculate refactoring priorities for legacy systems?▼

The best way to calculate refactoring priorities for legacy systems is applying the formula Priority = (Impact + Risk) x (6 - Effort). This scoring rubric evaluates technical debt severity against remediation effort to output a prioritized remediation plan.

Does this technical debt evaluation require specific dependencies or components?▼

No specific dependencies or components are required to evaluate technical debt. The process relies on applying a standardized scoring rubric to your existing monorepos, multi-repo ecosystems, or legacy systems to identify and prioritize refactoring tasks.

Related Skills

Explore More Software Engineering Skills→
apexradiusapexradius

code-health

Analyze code complexity, test coverage, duplication, dependency freshness, and type safety.

Official
Advanced
managedcodemanagedcode
4

mcaf-agile-delivery

Define delivery workflows with backlog, roles, ceremonies, and feedback rules.

Official
Intermediate
HomericIntelligenceHomericIntelligence
18

detect-code-smells

Detect code smells and complexity issues in codebases.

Official
Intermediate
act70255act70255

code-reviewer

Automate code reviews with static analysis and AI vulnerability detection.

Community
Advanced