tech-debt

Identify and prioritize technical debt using impact, risk, and effort scoring.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ilove323/comlan-skills --skill tech-debt-ilove323
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/ilove323/comlan-skills/tree/main/engineering/skills/tech-debt
Command: npx skills add https://github.com/ilove323/comlan-skills --skill tech-debt-ilove323

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify, classify, and prioritize technical debt to improve code health and maintainability.

Core Features & Use Cases

  • Debt discovery & classification: categorize debt into code, architecture, tests, dependencies, documentation, and infrastructure with concrete examples.
  • Prioritization framework: apply a scoring model based on impact, risk, and effort to generate a phased remediation plan.
  • ** backlog governance**: produce a prioritized list with estimated effort and a staged plan that can run in parallel with feature work.

Quick Start

Initiate a tech-debt review by cataloging known debt items, then apply the priority framework to generate a phased remediation plan.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I prioritize technical debt during backlog grooming?

Prioritize technical debt by applying a scoring framework based on impact, risk, and effort to cataloged items, generating a phased remediation plan that runs in parallel with feature work.

What is the best way to categorize code quality issues for a refactoring plan?

Categorize code quality issues by classifying technical debt into code, architecture, tests, dependencies, documentation, and infrastructure with concrete examples to structure refactoring plans.

How do I create a tech debt governance plan that reduces maintenance cost?

Create a tech debt governance plan by cataloging known debt items and applying a priority framework to output a prioritized list with estimated effort and staged remediation phases.

Can I estimate the effort required for architecture refactoring across software teams?

Yes, you can estimate effort for architecture refactoring by scoring known debt items based on their impact, risk, and effort, which produces a prioritized list with estimated effort levels.

What types of technical debt should I identify during an infrastructure audit?

During an infrastructure audit, identify technical debt across codebases, architecture decisions, tests, dependencies, documentation, and infrastructure to reduce friction and maintenance cost.