skills.rest
imclab
imclabOFFICIAL
Explore all skills by this author →
Website𝕏@TheIMCLabGitHub

tech-debt

Scan repositories for debt indicators and maintain a prioritized register in docs/tech-debt-register.md.

1|Updated May 3, 2026
Search Tags:#documentation#maintainability#technical debt#prioritization#sprint planning#duplication detection#code scanning
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill tech-debt-imclab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill tech-debt-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of scattered, undocumented technical debt that quietly slows teams down and causes recurring failures.

Core Features & Use Cases

  • Debt scanning and categorization: Detects debt indicators such as TODO/FIXME/HACK markers, deprecated usages, duplication patterns, and coarse complexity hotspots.
  • Debt register management: Supports adding new entries and maintaining a consistent register format with effort, impact, and sprint targeting.
  • Prioritization and reporting: Re-sorts items using an impact/frequency/effort scoring rule and produces sprint-ready summaries and trend signals.

Quick Start

Use the tech-debt skill to scan the codebase and update the register by saying: "tech-debt scan".

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I track and prioritize technical debt in my repository?▼

Track and prioritize technical debt by scanning codebases for TODO/FIXME markers, deprecated usages, and duplication patterns, then maintaining a structured register in docs/tech-debt-register.md with deterministic impact, frequency, and fix effort scores.

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

Scan code for technical debt indicators by running the tech-debt scan subcommand, which detects TODO/FIXME/HACK markers, deprecated usages, duplication patterns, and coarse complexity hotspots across the repository.

Can I integrate technical debt tracking into sprint planning workflows?▼

Integrate technical debt tracking into sprint planning by generating sprint-ready summaries and trend signals from the debt register, using impact, frequency, and fix effort scoring rules to re-sort prioritized items.

What's the best way to maintain a technical debt register for continuous maintenance?▼

Maintain a technical debt register by using subcommand-driven operations to add new entries and update existing ones, persisting results in docs/tech-debt-register.md with consistent effort, impact, and sprint targeting fields.

How does technical debt scoring work for prioritization and reporting?▼

Technical debt scoring works deterministically by evaluating impact, frequency, and fix effort metrics, re-sorting register items to produce sprint-ready summaries and trend signals for reporting over time.

Does tech-debt require any specific dependencies or external tools to run?▼

Tech-debt requires no external dependencies or components, operating through subcommand-driven commands including scan, add, prioritize, and report to manage and persist a structured debt register.

Related Skills

Explore More Software Engineering Skills→
FrancisVargaFrancisVarga

tech-debt

Scan codebases for debt indicators and prioritize repayment in a register.

Community
Intermediate
nuoyanruoshuinuoyanruoshui
47

tech-debt

Scan codebases for debt indicators and manage prioritized debt registers.

Community
Advanced
jackmcintyrejackmcintyre

python-refactoring

Analyze Python code for complexity, duplication, and best practices.

Community
Intermediate
tranhieutttranhieutt
70

tech-debt

Scan codebase markers and update the technical debt register.

Community
Advanced