tech-debt

Name: tech-debt
Availability: InStock
Author: whmathews15

Review technical debt mentions and generate a prioritized inventory with impact and effort classifications.

1|Updated Jun 28, 2026

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

Ready to run

npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill tech-debt-whmathews15

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/whmathews15/DEX-Personal-Operating-System/tree/main/.claude/skills/_available/engineering/tech-debt
Command: npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill tech-debt-whmathews15

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn scattered technical debt mentions into a clear, actionable backlog so important cleanup work does not get lost in project notes, meetings, or code review discussions.

Core Features & Use Cases

Debt Inventory: Collects technical debt items from project notes, meeting notes, and review discussions.
Impact and Effort Assessment: Organizes each item by affected component, business impact, estimated effort, and age.
Prioritization Matrix: Separates work into do now, plan for, quick wins, and defer so teams can make better scheduling decisions.
Use Case: A product engineering team can scan its recent meeting notes and identify which refactors are blocking delivery versus which cleanup tasks can wait.

Quick Start

Ask the skill to review your recent project notes and meeting summaries for technical debt, then rank each item by impact, effort, and age.

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 from meeting notes and code reviews?▼

A prioritization matrix organizes technical debt into four categories: do now, plan for, quick wins, and defer. It ranks items by business impact, estimated effort, and age to help teams schedule refactoring work effectively.

What is the best way to track refactoring tasks across an engineering project?▼

Tracking refactoring tasks requires building a debt inventory that captures affected components, business impact, and task age. This turns scattered project notes into a clear, actionable backlog so important cleanup work is not lost over time.

How does technical debt age tracking work for prioritization?▼

Technical debt age tracking logs when an issue was first mentioned in project notes or code reviews. Combining age with impact and effort classification ensures long-standing reliability issues receive appropriate priority in the refactoring backlog.

Can I use this to separate quick wins from critical refactors?▼

Yes, the prioritization matrix explicitly separates quick wins from critical refactors. It evaluates each technical debt item by its business impact and required effort, allowing teams to identify low-effort, high-impact tasks versus urgent, high-effort work.

When should I not use a technical debt prioritization matrix?▼

You should avoid using a technical debt prioritization matrix for immediate production incidents or real-time code review blocking issues. It is designed for tracking long-term refactors, cleanup, and reliability work rather than urgent operational fixes.