One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill tech-debt-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/tech-debt
Command: npx skills add https://github.com/MichaelSolati/mkai --skill tech-debt-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unmanaged technical debt slows development velocity, introduces hidden bugs, and makes codebases increasingly difficult to maintain over time, leading to wasted engineering effort and delayed feature releases.

Core Features & Use Cases

  • Automated Debt Scanning: Detects common tech debt indicators including TODO/FIXME/HACK comments, deprecated code markers, duplicated code blocks, oversized files and functions, and outdated dependencies, then categorizes each finding into architecture, code quality, test, documentation, dependency, or performance debt.
  • Manual Debt Entry: Add new technical debt items manually with custom descriptions, affected files, impact assessment, category, and estimated fix effort to capture debt not caught by automated scans.
  • Prioritization & Reporting: Re-sorts all debt items by a calculated priority score (impact multiplied by encounter frequency, divided by fix effort) to identify high-impact items for sprint planning, and generates trend reports to track debt growth or reduction over time, flagging items stuck in the backlog for more than 3 sprints.
  • Use Case: An engineering team preparing for a sprint can run a scan to catch new debt from the previous iteration, manually add any newly identified issues, prioritize the full debt register to select items to tackle in the upcoming sprint, and generate a report to share with stakeholders on overall codebase health.

Quick Start

Use the tech-debt skill to scan your current codebase for technical debt indicators and append the findings to your project's tech-debt-register.md file.

Frequently Asked Questions about tech-debt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan my codebase for technical debt and categorize the findings?

You can manually add technical debt items by providing custom descriptions, affected files, impact assessments, categories, and estimated fix efforts to capture issues missed by automated scans.

How do I prioritize technical debt items for sprint planning?

Technical debt prioritization for sprint planning uses a calculated priority score based on impact multiplied by encounter frequency, divided by fix effort, to identify high-impact items for remediation.

What is technical debt backlog management and how does it track codebase health?

Technical debt backlog management tracks codebase health by generating trend reports on debt growth or reduction over time, flagging specific items that have remained stuck in the backlog for more than 3 sprints.

Does technical debt scanning work with version-controlled codebases for engineering workflows?

Yes, technical debt scanning supports engineering workflows including sprint planning and codebase health audits specifically for teams using version-controlled codebases.

Can I manually add technical debt items not caught by automated codebase scans?

Yes, you can manually add technical debt items by inputting custom descriptions, affected files, impact assessments, categories, and estimated fix efforts to capture debt missed by automated scanning.

What is the best way to track codebase maintenance debt over time?

The best way to track codebase maintenance debt over time is by generating trend reports that monitor debt growth or reduction, automatically flagging items stuck in the backlog for over 3 sprints.