Skip to content
Agentmart
Submit a tool
This entry duplicates brooks-debt, which is the one we list in search.

brooks-debt

Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve…

Skill by Aaryan1524

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/aaryan1524-brooks-debt

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.

Use cases: backend, devops

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill name
brooks-debt
Description
Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.
License
MIT
Instructions
24 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • debt-guide.md

SKILL.md (first lines)

# Brooks-Lint — Tech Debt Assessment

## Setup

Read in order:

1. `../_brooks-shared/common.md` — Iron Law, Project Config, Report Template, Health Score
2. `../_brooks-shared/source-coverage.md` — book coverage, exceptions, tradeoffs
3. `../_brooks-shared/decay-risks.md` — symptom definitions and source attributions
4. `debt-guide.md` (this directory) — the debt classification framework

## Process

**Scope:** if the user did not describe the codebase or point to specific areas, apply
Auto Scope Detection (`../_brooks-shared/common.md`) first.

1. Scan for all six decay risks (Step 1 of the guide); list every finding before scoring
2. Apply the Pain × Spread priority formula and classify debt intent (Steps 2–3 of the guide)
3. Group findings by decay risk (Step 4 of the guide)
4. Output using the Report Template from common.md, plus the Debt Summary Table

**Mode line in report:** `Tech Debt Assessment`

From Aaryan1524/Codex_Skills, MIT.

More from Aaryan1524/Codex_Skills

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
Sep 12, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from Aaryan1524

Cite this page

brooks-debt skill. Agent Mart. https://agentmart.dev/skills/aaryan1524-brooks-debt (last updated 2026-10-24)