skills.rest
tranhieutt
tranhieuttCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt

Scan codebase markers and update the technical debt register.

70|42|Updated Mar 27, 2026
Search Tags:#prioritization#code-quality#code-scanning#sprint-planning#technical-debt#debt-register
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill tech-debt-tranhieutt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill tech-debt-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams lose visibility into architectural, quality, and documentation debt when TODOs, workarounds, and missing tests pile up without a consistent register, making sprint planning and risk management fragile and reactive. This skill enforces a disciplined workflow—scanning for debt indicators, logging new entries, prioritizing by impact and effort, and tracking status inside docs/technical/tech-debt.md—so every decision about debt is deliberate.

Core Features & Use Cases

  • Automated scanning: Identify TODO, FIXME, HACK markers, deprecated APIs, duplicated blocks, and overly large files or functions, then categorize the findings across architecture, code quality, tests, documentation, dependencies, and performance.
  • Register management: Prompt for manual additions with justified acceptance, update the markdown register, and score each item by impact times frequency divided by effort.
  • Sprint-ready reporting: Prioritize high-impact items, recommend fixes for upcoming sprints, and generate summary reports showing counts by category, effort sizes, trending direction, and flags for items idle for more than three sprints.

Quick Start

Use the tech-debt skill to scan the repository for indicators, refresh docs/technical/tech-debt.md, and note priority items for the next sprint.

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 across my codebase for sprint planning?▼

You can track technical debt by scanning your codebase for TODO, FIXME, and HACK markers, then logging them into a markdown register at docs/technical/tech-debt.md. This process categorizes entries by architecture, code quality, tests, documentation, dependencies, and performance for sprint planning.

What is the best way to prioritize technical debt items by impact and effort?▼

Technical debt items are prioritized using a scoring system that calculates impact multiplied by frequency, divided by effort. This scoring method helps identify high-impact items to recommend for fixes in upcoming sprints, ensuring deliberate risk management.

How do I scan my repository for technical debt indicators like duplicated blocks and deprecated APIs?▼

Scanning for technical debt indicators involves identifying TODO, FIXME, and HACK markers, deprecated APIs, duplicated blocks, and overly large files or functions across the repository. The findings are then categorized to update the debt register.

Can I generate sprint-ready reports showing technical debt counts by category and trending direction?▼

Yes, sprint-ready reporting summarizes technical debt by showing counts per category, effort sizes, and trending direction. It also flags items that have been idle for more than three sprints to highlight stale risks during planning.

Does managing a technical debt register require manual additions for workarounds and missing tests?▼

Managing a technical debt register requires prompting for manual additions with justified acceptance for workarounds and missing tests. These manual entries are then scored by impact and effort alongside automated scanning results.

Why does technical debt management flag items idle for more than three sprints?▼

Technical debt management flags items idle for more than three sprints to prevent accumulated risks from becoming fragile and reactive. This tracking ensures that stale architectural, quality, and documentation debt remains visible during sprint planning.

Related Skills

Explore More Software Engineering Skills→
easonlaoeasonlao

tech-debt

Scan codebases for debt indicators and maintain a prioritized register.

Community
Intermediate
camilooscargbaptistacamilooscargbaptista
7

tech-debt-prioritization

Prioritizes technical debt items using RIME scoring to rank remediation work.

Community
Intermediate
nikhillinitnikhillinit

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Community
Advanced
DonchitosDonchitos
23.7k

tech-debt

Scan codebases for technical debt indicators and maintain a categorized debt register.

Community
Intermediate