tech-debt

Identify, categorize, and prioritize technical debt with remediation plans.

Updated Mar 5, 2026

Search Tags:#code quality #refactoring #maintenance #technical debt #prioritization #tech debt

Ready to run

npx skills add https://github.com/8GG-Git/knowledge-work-plugins --skill tech-debt-8gg-git

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/8GG-Git/knowledge-work-plugins/tree/main/engineering/skills/tech-debt
Command: npx skills add https://github.com/8GG-Git/knowledge-work-plugins --skill tech-debt-8gg-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically identify, categorize, and prioritize technical debt to improve code quality and development velocity.

Core Features & Use Cases

Identification: Detects various types of technical debt including code, architecture, test, dependency, documentation, and infrastructure debt.
Categorization: Organizes identified debt into predefined types with associated risks.
Prioritization: Employs a framework to score debt based on impact, risk, and effort, generating a prioritized list.
Remediation Planning: Produces phased plans for addressing technical debt alongside feature development.

Quick Start

Run a technical debt audit and provide a prioritized list of refactoring items.

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 categorize technical debt across my codebase?▼

To identify technical debt, analyze your codebase to detect code, architecture, test, dependency, documentation, and infrastructure debt. Categorizing technical debt involves organizing these issues into predefined types with their associated risks to improve code quality and development velocity.

What is the best way to prioritize technical debt for refactoring?▼

The best way to prioritize technical debt is using a scoring framework that evaluates each item based on its impact, risk, and effort. Prioritizing technical debt this way generates a ranked list to help teams address critical refactoring tasks first while balancing feature development.

How do I create a technical debt remediation plan alongside feature development?▼

Creating a technical debt remediation plan involves producing phased schedules that integrate debt resolution with ongoing feature development. A technical debt remediation plan ensures that addressing architecture, code, and test debt progresses systematically without halting new feature delivery.

Can I run a technical debt audit for both code and infrastructure issues?▼

Yes, you can run a technical debt audit that covers both code and infrastructure issues. A technical debt audit detects various types including code, architecture, test, dependency, documentation, and infrastructure debt, providing a comprehensive overview of maintenance needs across your project.

What types of technical debt should I look for in a software engineering project?▼

In a software engineering project, the types of technical debt to look for include code, architecture, test, dependency, documentation, and infrastructure debt. Identifying these categories of technical debt allows teams to map associated risks and apply a structured scoring framework for prioritization.