Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Systematically identifies, scores, and prioritizes technical debt across codebases with impact analysis and detailed remediation roadmaps for engineering teams.
Systematically identifies, scores, and prioritizes technical debt across codebases with impact analysis and detailed remediation roadmaps for engineering teams.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Systematic technical debt assessment for engineering teams. Identifies, scores, and prioritizes debt across your codebase with business impact analysis and remediation roadmaps.
Debt Discovery โ Categorizes debt: architecture, code quality, dependency, testing, infrastructure, documentation Impact Scoring โ Rates each item on effort (1-5), risk (1-5), and business impact (1-5) using a weighted formula Cost Modeling โ Estimates carrying cost per sprint in developer-hours and dollars Remediation Roadmap โ Generates a prioritized paydown plan with quick wins, scheduled work, and strategic rewrites Executive Summary โ One-page board-ready report showing debt-to-velocity ratio and projected savings
Describe your system, stack, and known pain points. The agent audits systematically: "Audit our technical debt. We're a Node.js/React SaaS with 180K LOC, 12 engineers. Known issues: monolithic API, no integration tests, 3 deprecated dependencies, manual deployments."
Priority Score = (Risk ร 3) + (Business Impact ร 2) + (1/Effort ร 1) Higher score = fix first. Quick wins (low effort, high risk) surface to the top.
CategoryExamplesTypical Carrying CostArchitectureMonoliths, tight coupling, wrong patterns15-25% velocity dragCode QualityDuplication, god classes, no standards10-20% velocity dragDependenciesOutdated libs, security vulns, EOL frameworks5-15% + incident riskTestingNo tests, flaky tests, manual QA only20-40% bug-fix overheadInfrastructureManual deploys, no monitoring, snowflake servers10-30% ops overheadDocumentationNo onboarding docs, tribal knowledge2-4 weeks per new hire
Engineering teams spend 23-42% of development time on technical debt (Stripe Developer Report). Most don't measure it. What you don't measure, you can't manage. Built by AfrexAI โ AI-powered business operations tools. Need the full engineering context pack? Browse our AI Context Packs ($47) or try the free AI Revenue Calculator.
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.