New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Technical Debt Management

by cbrock84 in cbrock84/headcount

Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms.

MITAuto-check passedDevelopment

Install Technical Debt Management

skills CLI
$ npx skills add cbrock84/headcount --skill technical-debt-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount technical-debt-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/technology/skills/technical-debt-management .claude/skills/technical-debt-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
technical-debt-management
GitHub stars
2k
Token cost
~829 tokens
SKILL.md length
467 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms.

  • Tasks that involve Technical debt
  • SKILL.md covers Classify before prioritizing, Cost is a rate, not a total, Argue in the language of the… and Remediate incrementally, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Technical Debt Management is an agent skill from cbrock84/headcount. Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Development, covering Technical debt. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Tasks that involve Technical debt

Example prompts

  • “Use the technical-debt-management skill to make technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and…”
  • “/technical-debt-management”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Technical Debt Management loads about 829 tokens when it runs, and up to ~1k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 467 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~829
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 467 words, ~829 tokens.

Download SKILL.mdSave it as .claude/skills/technical-debt-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
technical-debt-management
description
Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.

Technical debt management

Debt is a deliberate trade: taking on future cost to move faster now. Most of what gets called debt is not that — it is mess, which was never a decision, or drift, where the world moved and the code did not. The distinction matters because the arguments and remedies differ.

Classify before prioritizing

  • Deliberate debt — a known shortcut with a reason. Has a principal and interest. Legitimate.
  • Mess — nobody chose it; it accumulated. No trade was made, so there is nothing to defend.
  • Drift — the code was right for a context that has changed. Neither shortcut nor carelessness.
  • Not debt at all — code someone dislikes, or would have written differently. Taste is not debt, and rewriting on taste is how remediation budgets get spent with nothing to show.

Cost is a rate, not a total

Debt matters proportional to how often you pay it. Ugly code in a module nobody has touched in three years costs nothing; a moderate awkwardness in the file every feature crosses costs continuously.

Measure by contact: change frequency, how long changes there take relative to elsewhere, how often changes there cause incidents, and how many people avoid the area. Overlay change frequency on complexity and the priorities become obvious and defensible — the expensive parts are where both are high, which is rarely where intuition points.

Argue in the language of the decision-maker

"The code is bad" loses to any feature request. What wins is the rate: this area consumes a disproportionate share of delivery time, causes a disproportionate share of incidents, and the gap widens.

Frame remediation as capacity recovery with a payback period — the same terms as finance:capital-allocation, which is where any large migration will eventually be judged.

Show full SKILL.md (180 more words)Show less

Remediate incrementally

Large rewrites fail at a well-documented rate: they take longer than estimated, deliver no value until the end, and are canceled halfway leaving two systems. Prefer strangling the old system gradually behind a stable interface, so value lands continuously and the work can stop at any point without leaving a mess.

Improve opportunistically where you are already working — the code you are touching anyway is the cheapest code to improve, and it is by definition the code that is being touched.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Present debt as a quality argument to someone accountable for delivery dates.
  • Prioritize by how bad code looks rather than how often it is paid for.
  • Start a rewrite with no value delivered until completion.
  • Classify taste as debt.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/technology/skills/technical-debt-management of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Technical Debt Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Technical Debt Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Technical Debt Management this skillcbrock84/headcount2k—~829Automated safety check: PassMIT
Systematic Code Refactoringluongnv89/claude-howto42k—~3kAutomated safety check: PassMIT
Code Simplification for ego-litecitrolabs/ego-lite17k—~1.2kAutomated safety check: PassMIT
Code Refactoring Workflowluongnv89/claude-howto42k—~3.1kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3814 repos~2.4kAutomated safety check: PassMIT
Ponytail Debt LedgerDietrichGebert/ponytail159k—~453Automated safety check: PassMIT

Similar skills

  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

  • Code Simplification for ego-lite

    citrolabs/ego-lite

    Finds and implements evidence-backed simplifications in the ego-lite repository, such as dead code, duplicated state and speculative abstractions, without hiding behavior changes.

    17k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Code Refactoring Workflow

    luongnv89/claude-howto

    Guides systematic, test-backed refactoring in the style of Martin Fowler, moving through research, planning and small incremental changes with your approval at each phase.

    42k GitHub stars~3.1k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed

  • Ponytail Debt Ledger

    DietrichGebert/ponytail

    Collects every ponytail: comment in a codebase into one debt ledger, flags shortcuts with no upgrade trigger and reports without changing any files.

    159k GitHub stars~453 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • FIXME Resolver

    tailcallhq/forgecode

    Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.

    7.6k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo

  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 21 days ago
    Auto-check passed

  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 21 days ago
    Auto-check passed

  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 21 days ago
    Auto-check passed

  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 21 days ago
    Auto-check passed

  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 21 days ago
    Auto-check passed

  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 21 days ago
    Auto-check passed

Categories

Questions about Technical Debt Management

What does Technical Debt Management do?

Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Technical Debt Management is an agent skill from cbrock84/headcount. Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms.

When should I use Technical Debt Management?

Technical Debt Management fits situations like: tasks that involve Technical debt.

How do I install Technical Debt Management in Claude Code?

Run `npx skills add cbrock84/headcount --skill technical-debt-management -a claude-code`. Or copy the skill folder (plugins/technology/skills/technical-debt-management in cbrock84/headcount) into .claude/skills/technical-debt-management in your project. Claude Code loads it when a task matches its description.

How do I install Technical Debt Management in Codex?

Run `npx skills add cbrock84/headcount --skill technical-debt-management -a codex`. Or copy the skill folder (plugins/technology/skills/technical-debt-management in cbrock84/headcount) into .agents/skills/technical-debt-management in your project. Codex loads it when a task matches its description.

Can I use Technical Debt Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill technical-debt-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-debt-management, .gemini/skills/technical-debt-management, .github/skills/technical-debt-management and .opencode/skills/technical-debt-management in your project.

What does Technical Debt Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Technical Debt Management is instructions for the agent only.

Does Technical Debt Management access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Technical Debt Management safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Technical Debt Management use?

Technical Debt Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Technical Debt Management use?

About 829 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 216 tokens, read only when the agent opens those files.

What are the alternatives to Technical Debt Management?

Skills that share tags, products or a category with Technical Debt Management: Systematic Code Refactoring (luongnv89/claude-howto, 42k stars), Code Simplification for ego-lite (citrolabs/ego-lite, 17k stars), Code Refactoring Workflow (luongnv89/claude-howto, 42k stars) and Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Technical Debt Management?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,016 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.