Brooks debt

Skill sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/brooks-debt

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 1,987+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

Install

npx -y skills add sickn33/agentic-awesome-skills --skill brooks-debt

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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...

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.2 KB, as published. Nobody here has run it

Brooks-Lint — Tech Debt Assessment

When to Use

Use this skill when you need 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...

Setup

Read ../_shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules
Read ../_shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs
Read ../_shared/decay-risks.md for symptom definitions and source attributions
Read debt-guide.md in this directory for the debt classification framework

Process

If the user has not described the codebase or pointed to specific areas: apply Auto Scope Detection from ../_shared/common.md to determine the assessment scope before proceeding.

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

Mode line in report: Tech Debt Assessment

Limitations

Use this skill only when the task clearly matches its upstream source and local project context.
Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.