Menu

Individual skill

tech-debt-burndown-planner

Quantifies technical debt into an actionable, prioritized burndown backlog with clear ROI estimates.

skills/productivity/tech-debt-burndown-planner/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Audit and convert sprawling, informal technical debt complaints into a rigorously prioritized, ROI-driven engineering burndown backlog ranked by Risk, Developer Drag, and Remediation Effort.

## When to Use

- Planning engineering allocation for technical debt sprints or quarterly OKRs.
- Convincing product managers to prioritize refactoring by translating tech debt into developer velocity and reliability metrics.
- Establishing an ongoing, sustainable 20% technical debt paydown workflow.

## What to Analyze

1. **Debt Categorization**: Architecture Debt (monolith coupling), Test Debt (flaky E2E tests), Tooling Debt (slow CI builds), Dependency Debt (EOL libraries).
2. **Developer Drag Factor (1-5)**: How many hours per engineer does this issue waste weekly?