technical-debt-tracker

Identify and quantify technical debt across a codebase for remediation planning.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill technical-debt-tracker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-debt-tracker
Source: https://github.com/s3nex-com/sdlc-skills-library/tree/main/skills/phase3/technical-debt-tracker
Command: npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill technical-debt-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical debt accumulates as suboptimal decisions, slows velocity, and increases maintenance costs, making long-term delivery unstable.

Core Features & Use Cases

  • Inventory and categorize debt across Architecture, Design, Code, Test, Dependency, Infrastructure, and Documentation.
  • Prioritize items using a structured scoring system and generate a debt register summary to guide sprint planning and governance.
  • Provide templates and processes for monthly reviews, debt item logging, and remediation budgeting.

Quick Start

Run an initial debt assessment to inventory all debt items, score them, and generate a prioritized backlog for the sprint.

Frequently Asked Questions about technical-debt-tracker

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

FAQPage Schema
How do I track and prioritize technical debt for sprint planning?▼

Track technical debt by applying a structured scoring system to inventory items across categories like Architecture, Code, and Test Debt. This generates a prioritized debt register to directly guide your sprint planning and remediation backlog.

What is the best way to inventory suboptimal code decisions for governance reporting?▼

Inventory suboptimal code decisions for governance reporting by categorizing them into Architecture, Design, Code, Test, Dependency, Infrastructure, and Documentation debt. This builds a standard debt register with executive summaries for reporting.

How do I run a technical debt assessment to build a remediation backlog?▼

Run a technical debt assessment by identifying and quantifying debt items across your codebase, scoring them based on impact, and generating a prioritized backlog. This enables deliberate remediation planning during sprint cycles.

Can I categorize technical debt across architecture, code, and infrastructure?▼

Yes, you can categorize technical debt across Architecture, Design, Code, Test, Dependency, Infrastructure, and Documentation. This structured categorization enables precise tracking and targeted remediation budgeting.

How does a structured debt scoring system work for monthly code reviews?▼

A structured debt scoring system works by applying a standard format to quantify debt items during monthly reviews. It updates the debt register and generates executive summaries to track remediation progress and velocity impacts.

When do I need a technical debt register for software maintenance?▼

You need a technical debt register when suboptimal decisions slow velocity and increase maintenance costs. It makes debt visible, prioritized, and remediated through structured logging, monthly reviews, and remediation budgeting.