Stats
Actions
Tags
From brooks-lint
Assesses tech debt by identifying, classifying, and prioritizing maintainability problems to build a refactoring roadmap. Draws on twelve classic engineering books.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brooks-lint:brooks-debtThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules
../_shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules../_shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs../_shared/decay-risks.md for symptom definitions and source attributionsdebt-guide.md in this directory for the debt classification frameworkIf 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.
Mode line in report: Tech Debt Assessment
npx claudepluginhub hyhmrright/brooks-lint --plugin brooks-lintIdentifies, categorizes, and prioritizes technical debt across code, architecture, tests, dependencies, docs, and infrastructure. Scores by impact, risk, effort; outputs remediation plans.
Measure, prioritize, and address technical debt. Classify debt by impact and effort. Build paydown roadmap. Use when evaluating system health or planning refactoring.
Systematically identify, classify, and prioritize technical debt in codebases using SQALE model and Fowler's quadrant. Guides static analysis, debt register creation, and ROI-based remediation.