tech-debt-tracker

Scan code and dependencies to categorize and prioritize technical debt.

2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/EvanPluchart/kyomu --skill tech-debt-tracker-evanpluchart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt-tracker
Source: https://github.com/EvanPluchart/kyomu/tree/main/.claude/skills/tech-debt-tracker
Command: npx skills add https://github.com/EvanPluchart/kyomu --skill tech-debt-tracker-evanpluchart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies and prioritizes technical debt so you can focus effort on the highest-impact remediation instead of relying on ad-hoc reviews.

Core Features & Use Cases

It scans a project for common debt signals like TODO/FIXME patterns, duplicated code, overly complex or long files, outdated or vulnerable dependencies, missing/weak typing, and low test coverage, then classifies each finding by category (Securite, Performance, Maintenabilite, Obsolescence) and scores it by impact and effort to produce a prioritization-ready report. It fits workflows where teams need periodic quality audits, pre-sprint risk reduction before major changes, or a structured input for deeper refactoring and dependency-focused analysis.

Quick Start

Ask the AI to run the tech-debt-tracker in Mode A with --scan and generate a markdown report that includes the matrix of impact versus effort and a remediation plan compatible with /refactor-planner.

Frequently Asked Questions about tech-debt-tracker

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

FAQPage Schema
How do I identify and prioritize technical debt in a software project?

Identifying and prioritizing technical debt involves scanning code for TODO patterns, duplicated code, complex files, outdated dependencies, and low test coverage. The tracker classifies findings by category and scores them by impact versus effort to produce a remediation-ready report.

What is the best way to plan refactoring before a major sprint?

The best way to plan refactoring is running a pre-sprint technical debt audit to reduce risk. Scanning for maintainability issues and vulnerability indicators produces a prioritization matrix that highlights high-impact, low-effort fixes to schedule first.

Can I generate an executive report on code maintainability and dependency obsolescence?

Yes, generating an executive report on code maintainability and dependency obsolescence is supported. The tracker scans for debt signals, categorizes them into Security, Performance, Maintainability, and Obsolescence, and outputs a structured markdown report for engineering planning.

Does the technical debt tracker work for targeted domain focus like security auditing?

Yes, the technical debt tracker works for targeted domain focus such as security or performance auditing. It scans specific dependency and code indicators within the selected domain to classify findings and generate focused remediation plans.

How do I use a prioritization matrix to plan dependency updates and refactoring?

Using a prioritization matrix to plan dependency updates and refactoring requires scoring each finding by remediation impact and effort. The tracker generates this matrix to help teams focus on high-impact technical debt fixes rather than relying on ad-hoc reviews.