tech-debt

Identify, categorize, and prioritize technical debt across codebases.

Updated Aug 23, 2026

Search Tags:#refactoring #prioritization #code-quality #dependency-management #test-coverage #technical-debt #architecture-debt

Ready to run

npx skills add https://github.com/SMOrchestra-ai/smorch-brain --skill tech-debt-smorchestra-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/SMOrchestra-ai/smorch-brain/tree/main/plugins/engineering/skills/tech-debt
Command: npx skills add https://github.com/SMOrchestra-ai/smorch-brain --skill tech-debt-smorchestra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps engineering teams systematically identify, categorize, and prioritize technical debt so teams can reduce risk, speed up delivery, and improve long-term maintainability.

Core Features & Use Cases

Comprehensive Categorization: Classifies debt into code, architecture, tests, dependencies, documentation, and infrastructure to surface the root causes.
Prioritization Framework: Scores items by impact, risk, and effort and calculates priority using the provided formula to create an objective remediation order.
Actionable Remediation Plans: Produces estimated effort, business justification, and phased plans that can be scheduled alongside feature work during sprint planning.

Quick Start

Run a technical debt audit across the codebase and return a prioritized list of issues with impact, risk, effort, and a phased remediation 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 across a codebase for remediation?▼

Prioritize technical debt by scoring issues based on impact, risk, and effort to create an objective remediation order. This approach categorizes debt into code, architecture, tests, dependencies, and infrastructure to surface root causes.

What are the common categories of technical debt I should look for during an audit?▼

Common categories of technical debt include code quality issues, architecture debt, test coverage gaps, dependency management risks, documentation gaps, and infrastructure health problems. Categorizing debt helps surface the root causes affecting long-term maintainability.

How can I generate a phased technical debt remediation plan for sprint planning?▼

Generate a phased technical debt remediation plan by scoring items with estimated effort and business justification. This produces actionable schedules suitable for integrating refactoring tasks alongside feature work during sprint planning.

Does this technical debt scoring framework require specific dependency or infrastructure tools?▼

No specific dependency or infrastructure tools are required to use this technical debt scoring framework. It applies to engineering teams performing code quality audits, architecture reviews, and infrastructure health evaluations across any codebase.

What is the best way to assess architecture debt and test coverage gaps together?▼

The best way to assess architecture debt and test coverage gaps together is to perform a comprehensive codebase audit. This process classifies debt into distinct categories and scores prioritized items to reduce risk and speed up delivery.