technical-debt-cataloger

Document, prioritize, and plan remediation for technical debt across software projects.

1|Updated Jan 22, 2026

Search Tags:#code quality #architecture #remediation #technical debt #prioritization #sustainability

Ready to run

npx skills add https://github.com/Ethical-AI-Syndicate/skills --skill technical-debt-cataloger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: technical-debt-cataloger
Source: https://github.com/Ethical-AI-Syndicate/skills/tree/main/technical-debt-cataloger
Command: npx skills add https://github.com/Ethical-AI-Syndicate/skills --skill technical-debt-cataloger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a systematic way to document, prioritize, and plan the remediation of technical debt, making it visible and manageable for stakeholders.

Core Features & Use Cases

Systematic Documentation: Captures details of technical debt, including type, impact, and remediation effort.
Prioritization Framework: Uses impact, urgency, and effort scores to calculate a priority score for each debt item.
Remediation Planning: Recommends timing for addressing debt and suggests capacity allocation for remediation.
Use Case: After a development sprint, use this skill to log newly identified code complexities, architectural limitations, or outdated documentation, ensuring they are tracked and addressed proactively.

Quick Start

Use the technical-debt-cataloger skill to document a new piece of technical debt with title 'Slow database queries' in the 'users' module.

Frequently Asked Questions about technical-debt-cataloger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prioritize technical debt across different software modules?▼

Technical debt prioritization uses impact, urgency, and effort scores to calculate a priority score for each item. This framework systematically quantifies code, architecture, test, documentation, and infrastructure debt to recommend optimal capacity allocation and remediation timing.

What is the best way to track architectural limitations found during a sprint?▼

Systematic technical debt documentation captures architectural limitations by logging details like type, impact, and remediation effort. This ensures newly identified debt is tracked proactively and made manageable for stakeholders after development sprints.

How do I plan capacity allocation for technical debt remediation?▼

Remediation planning recommends capacity allocation by quantifying the impact of technical debt and estimating the effort required to fix it. This allows teams to balance new feature development with necessary sustainability and code quality improvements.

Can I document infrastructure debt and code complexity using a single framework?▼

Yes, a technical debt cataloger supports tracking multiple debt types including code, architecture, test, documentation, and infrastructure debt. It provides a unified framework to document complexities and quantify their impact across software projects.

Does technical debt tracking work without external dependencies?▼

Technical debt cataloging works without external dependencies, relying solely on internal references to document and prioritize debt. It independently calculates priority scores and recommends remediation timing using impact, urgency, and effort metrics.