Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Identifies, analyzes, prioritizes, and tracks technical debt across code, architecture, tests, documentation, dependencies, and infrastructure for data-drive...
Identifies, analyzes, prioritizes, and tracks technical debt across code, architecture, tests, documentation, dependencies, and infrastructure for data-drive...
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.
Tier: POWERFUL ๐ฅ Category: Engineering Process Automation Expertise: Code Quality, Technical Debt Management, Software Engineering
Tech debt is one of the most insidious challenges in software development - it compounds over time, slowing down development velocity, increasing maintenance costs, and reducing code quality. This skill provides a comprehensive framework for identifying, analyzing, prioritizing, and tracking technical debt across codebases. Tech debt isn't just about messy code - it encompasses architectural shortcuts, missing tests, outdated dependencies, documentation gaps, and infrastructure compromises. Like financial debt, it accrues "interest" through increased development time, higher bug rates, and reduced team velocity.
This skill offers three interconnected tools that form a complete tech debt management system: Debt Scanner - Automatically identifies tech debt signals in your codebase Debt Prioritizer - Analyzes and prioritizes debt items using cost-of-delay frameworks Debt Dashboard - Tracks debt trends over time and provides executive reporting Together, these tools enable engineering teams to make data-driven decisions about tech debt, balancing new feature development with maintenance work.
โ See references/debt-frameworks.md for details
Set up debt scanning infrastructure Establish debt taxonomy and scoring criteria Scan initial codebase and create baseline inventory Train team on debt identification and reporting
Integrate debt tracking into sprint planning Establish debt budgets and allocation rules Create stakeholder reporting templates Set up automated debt scanning in CI/CD
Refine scoring algorithms based on team feedback Implement trend analysis and predictive metrics Create specialized debt reduction initiatives Establish cross-team debt coordination processes
Continuous improvement of detection algorithms Advanced analytics and prediction models Integration with planning and project management tools Organization-wide debt management best practices
Quantitative Metrics: 25% reduction in debt interest rate within 6 months 15% improvement in development velocity 30% reduction in production defects 20% faster code review cycles Qualitative Metrics: Improved developer satisfaction scores Reduced context switching during feature development Faster onboarding for new team members Better predictability in feature delivery timelines
Problem: Spending too much time analyzing debt instead of fixing it. Solution: Set time limits for analysis, use "good enough" scoring for most items.
Problem: Trying to eliminate all debt instead of managing it. Solution: Focus on high-impact debt, accept that some debt is acceptable.
Problem: Prioritizing technical elegance over business value. Solution: Always tie debt work to business outcomes and customer impact.
Problem: Some teams adopt practices while others ignore them. Solution: Make debt tracking part of standard development workflow.
Problem: Building complex debt management systems that nobody uses. Solution: Start simple, iterate based on actual usage patterns. Technical debt management is not just about writing better code - it's about creating sustainable development practices that balance short-term delivery pressure with long-term system health. Use these tools and frameworks to make informed decisions about when and how to invest in debt reduction.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.