Categorize and prioritize technical debt into a phased remediation plan.
npx skills add https://github.com/alo-exp/silver-bullet --skill tech-debt-alo-exp
Please help me install this Agent Skill. Skill: tech-debt Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/engineering-tech-debt Command: npx skills add https://github.com/alo-exp/silver-bullet --skill tech-debt-alo-exp
Systematically identify, categorize, and prioritize technical debt across a codebase to prevent slowdowns and regressions, enabling focused, timely improvements.
Run the priority workflow on your repository to generate the remediation plan.
High-intent search queries and answers about installing and using this skill.
Prioritize technical debt by classifying items into categories like code, architecture, and test debt, then scoring them by Impact, Risk, and Effort. This generates a phased remediation plan with itemized effort estimates and business justifications for your backlog.
Categorize technical debt using a structured taxonomy that covers code debt, architecture debt, test debt, dependency debt, documentation debt, and infrastructure debt. This classification enables systematic prioritization and targeted refactoring across diverse software projects.
Generate a refactoring backlog by applying a structured scoring formula to identified debt, evaluating Impact, Risk, and Effort. The resulting prioritized backlog includes estimated effort and business justifications to guide sprint planning and focused improvements.
Yes, a unified prioritization framework can assess both code debt and infrastructure debt. It systematically evaluates diverse debt types across your projects, applying consistent Impact, Risk, and Effort scoring to produce a cohesive remediation plan.
Generate a phased remediation plan when technical debt causes development slowdowns or system regressions. Running a priority workflow on your repository identifies duplicated logic, brittle modules, and outdated dependencies to guide timely improvements.
Test debt and dependency debt slow development by introducing flaky tests and outdated libraries, which increase maintenance overhead. Identifying and remediating these issues through structured scoring prevents regressions and ensures focused, timely improvements.
rm2thaddeusAnalyze codebases for architecture, quality, security, performance, and maintainability.
sun2443Categorize and prioritize technical debt with impact, risk, and effort scores.
KrismithReddy12Calculate a weighted 0-10 code quality score from linters and test runners.
Tonybleything76Scan codebases to identify, prioritize, and track technical debt.
