tech-debt

Scan codebase indicators, maintain a debt register, and generate sprint-ready reports.

Updated Apr 4, 2026

Search Tags:#code quality #documentation #maintenance #prioritization #sprint planning #tech debt #codebase scanning

Ready to run

npx skills add https://github.com/WindXRan/y3td --skill tech-debt-windxran

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/WindXRan/y3td --skill tech-debt-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you prevent technical debt from silently accumulating by identifying recurring debt signals, recording them in a single register, and guiding repayment scheduling.

Core Features & Use Cases

Debt scanning: Finds common indicators like TODO/FIXME/HACK markers, deprecated usage, duplication, and overly large files/functions, then groups findings by debt category.
Debt register management: Adds new debt entries with category and estimated effort, and supports re-prioritization based on impact, frequency, and fix effort.
Sprint-ready reporting: Generates a read-only status report with category counts, effort totals, trends, and stale-item flags (older than 3 sprints).

Quick Start

Ask the AI to run tech-debt in scan mode and write the findings to docs/tech-debt-register.md.

Frequently Asked Questions about tech-debt

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

FAQPage Schema

How do I track technical debt in my codebase?▼

Track technical debt by scanning for indicators like TODO/FIXME markers and deprecated usage, then maintain a structured register in docs/tech-debt-register.md to categorize and prioritize entries for repayment.

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

Prioritize technical debt for sprint planning by re-scoring existing register entries based on impact, frequency, and fix effort, then generate a read-only summary with category counts and stale-item flags.

How do I scan for technical debt indicators like TODO and FIXME?▼

Scan for technical debt indicators by running in scan mode to identify TODO/FIXME/HACK markers, code duplication, and overly large files, grouping findings by architecture, tests, or dependency categories.

Can I automatically document technical debt in a markdown register?▼

You can document technical debt in a markdown register by enabling optional safe writes to docs/tech-debt-register.md, adding new entries with estimated effort and debt category information.

How does technical debt categorization work for code maintenance?▼

Technical debt categorization for code maintenance works by grouping scanned findings into architecture, code quality, tests, documentation, dependency, or performance categories to guide repayment scheduling.

What are the limitations of tracking technical debt manually?▼

Manual tracking lacks sprint-ready reporting and stale-item detection older than 3 sprints, whereas automated scanning maintains a structured debt register with continuous effort totals and trend visibility.