tech-debt

Name: tech-debt
Availability: InStock
Author: NuoYan

Scan codebases for debt indicators and manage prioritized debt registers.

47|12|Updated Jun 14, 2026

Search Tags:#technical debt #prioritization #sprint planning #codebase analysis #software maintenance #debt register

Ready to run

npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill tech-debt-nuoyanruoshui

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps development teams systematically discover, document, prioritize, and report technical debt instead of letting maintenance risks remain scattered across the codebase.

Core Features & Use Cases

Debt Scanning: Find TODO, FIXME, HACK, deprecated markers, duplication, oversized files, and overly long functions.
Debt Register Management: Add categorized entries with impact, effort, rationale, affected files, and sprint planning information.
Prioritization and Reporting: Re-rank debt by impact, encounter frequency, and fix effort, then summarize category totals, trends, and aging items.
Use Case: A team can scan a Godot project for accumulated maintenance issues, review the findings, approve them for the debt register, and schedule the highest-impact items for an upcoming sprint.

Quick Start

Use the tech-debt skill with the scan subcommand to inspect the codebase and propose entries for the technical debt register.

Frequently Asked Questions about tech-debt

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

FAQPage Schema

How do I find and track technical debt across a software codebase?▼

To track technical debt across a software codebase, you scan for indicators like TODO, FIXME, HACK markers, duplication, and oversized files, then document them in a categorized register with impact and effort estimates.

What is a technical debt register and how does it help with sprint planning?▼

A technical debt register is a categorized list of maintenance issues with impact, effort, and rationale estimates. It aids sprint planning by allowing teams to re-rank debt by impact and fix effort, scheduling the highest-priority items for upcoming sprints.

How do I prioritize technical debt items for maintenance?▼

You prioritize technical debt items by collecting impact and effort estimates, then re-ranking them based on impact, encounter frequency, and fix effort to identify the highest-priority maintenance tasks for your codebase.

Can I scan a Godot project for accumulated codebase maintenance issues?▼

Yes, you can scan a Godot project for accumulated codebase maintenance issues. The scanning process identifies debt indicators like deprecated markers and overly long functions, proposes entries for the debt register, and schedules high-impact items for sprints.

What is the best way to report technical debt trends and aging items?▼

The best way to report technical debt trends and aging items is to summarize category totals and track aging entries from the debt register, preserving existing entries while requesting confirmation before writing any changes to the register.