{ "schemaVersion": "1.0", "item": { "slug": "tech-debt-tracker", "name": "Tech Debt Tracker", "source": "tencent", "type": "skill", "category": "ꕈēŽ‡ęå‡", "sourceUrl": "https://clawhub.ai/alirezarezvani/tech-debt-tracker", "canonicalUrl": "https://clawhub.ai/alirezarezvani/tech-debt-tracker", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/tech-debt-tracker", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=tech-debt-tracker", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md", "assets/historical_debt_2024-01-15.json", "assets/historical_debt_2024-02-01.json", "assets/sample_codebase/src/frontend.js", "assets/sample_codebase/src/payment_processor.py" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/tech-debt-tracker" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/tech-debt-tracker", "agentPageUrl": "https://openagent3.xyz/skills/tech-debt-tracker/agent", "manifestUrl": "https://openagent3.xyz/skills/tech-debt-tracker/agent.json", "briefUrl": "https://openagent3.xyz/skills/tech-debt-tracker/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Tech Debt Tracker", "body": "Tier: POWERFUL šŸ”„\nCategory: Engineering Process Automation\nExpertise: Code Quality, Technical Debt Management, Software Engineering" }, { "title": "Overview", "body": "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.\n\nTech 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." }, { "title": "What This Skill Provides", "body": "This skill offers three interconnected tools that form a complete tech debt management system:\n\nDebt Scanner - Automatically identifies tech debt signals in your codebase\nDebt Prioritizer - Analyzes and prioritizes debt items using cost-of-delay frameworks\nDebt Dashboard - Tracks debt trends over time and provides executive reporting\n\nTogether, these tools enable engineering teams to make data-driven decisions about tech debt, balancing new feature development with maintenance work." }, { "title": "Technical Debt Classification Framework", "body": "ā†’ See references/debt-frameworks.md for details" }, { "title": "Phase 1: Foundation (Weeks 1-2)", "body": "Set up debt scanning infrastructure\nEstablish debt taxonomy and scoring criteria\nScan initial codebase and create baseline inventory\nTrain team on debt identification and reporting" }, { "title": "Phase 2: Process Integration (Weeks 3-4)", "body": "Integrate debt tracking into sprint planning\nEstablish debt budgets and allocation rules\nCreate stakeholder reporting templates\nSet up automated debt scanning in CI/CD" }, { "title": "Phase 3: Optimization (Weeks 5-6)", "body": "Refine scoring algorithms based on team feedback\nImplement trend analysis and predictive metrics\nCreate specialized debt reduction initiatives\nEstablish cross-team debt coordination processes" }, { "title": "Phase 4: Maturity (Ongoing)", "body": "Continuous improvement of detection algorithms\nAdvanced analytics and prediction models\nIntegration with planning and project management tools\nOrganization-wide debt management best practices" }, { "title": "Success Criteria", "body": "Quantitative Metrics:\n\n25% reduction in debt interest rate within 6 months\n15% improvement in development velocity\n30% reduction in production defects\n20% faster code review cycles\n\nQualitative Metrics:\n\nImproved developer satisfaction scores\nReduced context switching during feature development\nFaster onboarding for new team members\nBetter predictability in feature delivery timelines" }, { "title": "1. Analysis Paralysis", "body": "Problem: Spending too much time analyzing debt instead of fixing it.\nSolution: Set time limits for analysis, use \"good enough\" scoring for most items." }, { "title": "2. Perfectionism", "body": "Problem: Trying to eliminate all debt instead of managing it.\nSolution: Focus on high-impact debt, accept that some debt is acceptable." }, { "title": "3. Ignoring Business Context", "body": "Problem: Prioritizing technical elegance over business value.\nSolution: Always tie debt work to business outcomes and customer impact." }, { "title": "4. Inconsistent Application", "body": "Problem: Some teams adopt practices while others ignore them.\nSolution: Make debt tracking part of standard development workflow." }, { "title": "5. Tool Over-Engineering", "body": "Problem: Building complex debt management systems that nobody uses.\nSolution: Start simple, iterate based on actual usage patterns.\n\nTechnical 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." } ], "body": "Tech Debt Tracker\n\nTier: POWERFUL šŸ”„\nCategory: Engineering Process Automation\nExpertise: Code Quality, Technical Debt Management, Software Engineering\n\nOverview\n\nTech 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.\n\nTech 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.\n\nWhat This Skill Provides\n\nThis skill offers three interconnected tools that form a complete tech debt management system:\n\nDebt Scanner - Automatically identifies tech debt signals in your codebase\nDebt Prioritizer - Analyzes and prioritizes debt items using cost-of-delay frameworks\nDebt Dashboard - Tracks debt trends over time and provides executive reporting\n\nTogether, these tools enable engineering teams to make data-driven decisions about tech debt, balancing new feature development with maintenance work.\n\nTechnical Debt Classification Framework\n\nā†’ See references/debt-frameworks.md for details\n\nImplementation Roadmap\nPhase 1: Foundation (Weeks 1-2)\nSet up debt scanning infrastructure\nEstablish debt taxonomy and scoring criteria\nScan initial codebase and create baseline inventory\nTrain team on debt identification and reporting\nPhase 2: Process Integration (Weeks 3-4)\nIntegrate debt tracking into sprint planning\nEstablish debt budgets and allocation rules\nCreate stakeholder reporting templates\nSet up automated debt scanning in CI/CD\nPhase 3: Optimization (Weeks 5-6)\nRefine scoring algorithms based on team feedback\nImplement trend analysis and predictive metrics\nCreate specialized debt reduction initiatives\nEstablish cross-team debt coordination processes\nPhase 4: Maturity (Ongoing)\nContinuous improvement of detection algorithms\nAdvanced analytics and prediction models\nIntegration with planning and project management tools\nOrganization-wide debt management best practices\nSuccess Criteria\n\nQuantitative Metrics:\n\n25% reduction in debt interest rate within 6 months\n15% improvement in development velocity\n30% reduction in production defects\n20% faster code review cycles\n\nQualitative Metrics:\n\nImproved developer satisfaction scores\nReduced context switching during feature development\nFaster onboarding for new team members\nBetter predictability in feature delivery timelines\nCommon Pitfalls and How to Avoid Them\n1. Analysis Paralysis\n\nProblem: Spending too much time analyzing debt instead of fixing it. Solution: Set time limits for analysis, use \"good enough\" scoring for most items.\n\n2. Perfectionism\n\nProblem: Trying to eliminate all debt instead of managing it. Solution: Focus on high-impact debt, accept that some debt is acceptable.\n\n3. Ignoring Business Context\n\nProblem: Prioritizing technical elegance over business value. Solution: Always tie debt work to business outcomes and customer impact.\n\n4. Inconsistent Application\n\nProblem: Some teams adopt practices while others ignore them. Solution: Make debt tracking part of standard development workflow.\n\n5. Tool Over-Engineering\n\nProblem: Building complex debt management systems that nobody uses. Solution: Start simple, iterate based on actual usage patterns.\n\nTechnical 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." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/alirezarezvani/tech-debt-tracker", "publisherUrl": "https://clawhub.ai/alirezarezvani/tech-debt-tracker", "owner": "alirezarezvani", "version": "2.1.1", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/tech-debt-tracker", "downloadUrl": "https://openagent3.xyz/downloads/tech-debt-tracker", "agentUrl": "https://openagent3.xyz/skills/tech-debt-tracker/agent", "manifestUrl": "https://openagent3.xyz/skills/tech-debt-tracker/agent.json", "briefUrl": "https://openagent3.xyz/skills/tech-debt-tracker/agent.md" } }