tech-debt

Name: tech-debt
Availability: InStock
Author: davekilleen

Scan projects and meeting notes to categorize technical debt by impact and effort.

461|129|Updated Jan 26, 2026

Search Tags:#code quality #refactoring #prioritization #engineering management #tech debt #technical debt review

Ready to run

npx skills add https://github.com/davekilleen/Dex --skill tech-debt-davekilleen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/davekilleen/Dex/tree/main/.claude/skills/_available/engineering/tech-debt
Command: npx skills add https://github.com/davekilleen/Dex --skill tech-debt-davekilleen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common issue of accumulating technical debt by providing a structured way to identify, categorize, and prioritize it, preventing it from being lost in scattered notes.

Core Features & Use Cases

Automated Discovery: Scans projects and meeting notes for mentions of technical debt.
Categorization: Groups identified debt by impact (critical, high, medium, low) and estimated effort.
Prioritization: Generates a matrix to help decide which debt items to address first.
Use Case: A development team can use this Skill to regularly review their codebase and project documentation, ensuring that critical technical debt is identified and scheduled for resolution before it significantly impacts velocity or stability.

Quick Start

Run the tech debt review for the entire project.

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?▼

Categorizing technical debt involves evaluating each item's impact level—critical, high, medium, or low—and pairing it with the estimated effort required for resolution to guide engineering management decisions.

What's the best way to track technical debt mentioned in meeting notes?▼

This automated discovery scans project documentation and meeting notes to identify scattered technical debt items, preventing them from being lost and ensuring they are scheduled for resolution.

How does a technical debt review impact development velocity?▼

A technical debt review impacts development velocity by identifying critical codebase issues and scheduling them for resolution before they significantly impact stability or slow down future feature delivery.

Can I use this for engineering management prioritization of code refactoring?▼

Yes, engineering management can use this for code refactoring prioritization by reviewing a generated matrix that aligns debt items by impact and effort to effectively manage codebase health.

Do I need a specific tool to categorize code quality issues by impact and effort?▼

No specific tool is needed to categorize code quality issues; the process directly groups identified technical debt by impact and estimated effort to build a prioritization matrix.