Menu

Individual skill

tech-debt-assessor

Inventories technical debt across a codebase and prioritizes it by cost-of-delay versus effort, producing a ranked paydown list. Use when debt is accumulating but it's unclear what to fix first.

skills/architecture/tech-debt-assessor/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

Turn a vague sense that "the codebase has a lot of debt" into a ranked, justified paydown list — assessing each item by what it actually costs to keep living with it, versus what it costs to fix.

## When to Use

- Technical debt is accumulating and it's unclear what to tackle first.
- Justifying debt-paydown work to stakeholders who need a reason beyond "it's messy."
- Planning a cleanup sprint and needing to pick the highest-value targets.

Differs from [Refactor Expert](../../development/refactor-expert/): that skill simplifies one specific piece of code; this one operates at portfolio level across the codebase, deciding *what* is worth refactoring at all.

## What to Analyze