tech-debt

Identify, categorize, and prioritize technical debt across code and infrastructure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically identify, categorize, and prioritize technical debt, ensuring that code quality and maintainability are addressed proactively.

Core Features & Use Cases

  • Identification: Detects various forms of technical debt including code, architecture, test, dependency, documentation, and infrastructure debt.
  • Categorization: Organizes identified debt into distinct types with examples and associated risks.
  • Prioritization: Employs a framework to score debt based on impact, risk, and effort, generating a prioritized list.
  • Remediation Planning: Produces a phased plan for addressing technical debt alongside feature development.
  • Use Case: A development team can use this skill to conduct a quarterly technical debt audit, receiving a prioritized backlog of refactoring tasks with clear justifications.

Quick Start

Run a technical debt audit and provide a prioritized list of refactoring items.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I identify and categorize technical debt in my codebase?

Identify technical debt by scanning your codebase to detect code, architecture, test, dependency, documentation, and infrastructure debt. This categorization organizes distinct debt types with examples and associated risks for systematic management.

What is the best way to prioritize technical debt for a refactoring backlog?

Prioritize technical debt using a framework that scores items based on impact, risk, and effort. This generates a prioritized list to help teams address the most critical refactoring tasks first.

How do I create a phased remediation plan for technical debt alongside feature development?

Create a phased remediation plan by evaluating your prioritized technical debt backlog against development velocity. This facilitates systematic software maintainability management without halting feature delivery.

Can I conduct a quarterly technical debt audit for software maintenance?

Yes, you can conduct a quarterly technical debt audit to receive a prioritized backlog of refactoring tasks. This proactive approach ensures code quality and maintainability are systematically addressed.

What types of technical debt can be systematically managed for development velocity?

Systematically manage code, architecture, testing, dependency, documentation, and infrastructure technical debt. Addressing these distinct types ensures long-term software maintainability and sustained development velocity.

Why does technical debt accumulate and require a prioritization framework?

Technical debt accumulates from trade-offs in software development and requires a prioritization framework based on impact, risk, and effort to generate a clear phased remediation plan.