skills.rest
qa-aman
qa-amanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt

Identify and prioritize technical debt with debt-type classification and test seams.

19|3|Updated Feb 28, 2026
Search Tags:#refactoring#prioritization#test-coverage#legacy-code#tech-debt#seams#debt-ticket
One-click install
npx skills add https://github.com/qa-aman/claude-skills --skill tech-debt-qa-aman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/qa-aman/claude-skills/tree/main/skills/by-role/engineer/tech-debt
Command: npx skills add https://github.com/qa-aman/claude-skills --skill tech-debt-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document and prioritize technical debt. Focuses on identifying debt, classifying it, and planning safe refactors with test seams.

Core Features & Use Cases

  • Define debt items with specifics (location, impact, symptom)
  • Classify the debt type (Reckless/Deliberate, etc.) and urgency
  • Find seams to insert tests without editing production code
  • Estimate cost to fix and impact on delivery
  • Produce a concrete debt-ticket with fix plan

Quick Start

Describe a debt item in the template and outline the seam tests to enable safe refactoring.

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 in legacy code for refactoring?▼

To prioritize technical debt in legacy code, classify items by type and urgency, estimate fix cost versus delivery impact, and rank them in the backlog to guide safe refactoring. This produces a structured debt-ticket with a concrete fix plan.

What are seams in technical debt management and how do they work?▼

Seams in technical debt management are places in legacy code where you can insert test behavior without editing production code. Finding them enables test-first refactoring, allowing safe modification of high-change areas by establishing test coverage before altering logic.

How do I document technical debt items for my development team?▼

You document technical debt items using a structured template capturing the location, impact, and symptoms of the debt. This standardizes record-keeping, ensuring the team has clear details for classifying debt type and planning subsequent refactors.

Can I use this approach for technical debt in high-change areas of a codebase?▼

Yes, this approach specifically applies to codebases with high-change areas and legacy modules. It helps manage technical debt by discovering test seams and estimating the fix cost, ensuring refactors in actively modified code are structured and safe.

What is the best way to classify technical debt types before planning a refactor?▼

The best way to classify technical debt types before planning a refactor is to categorize them by origin, such as reckless or deliberate debt. This informs the urgency and prioritization of the debt-ticket, guiding the fix plan and test seam strategy.

Related Skills

Explore More Software Engineering Skills→
Kingdaddy007Kingdaddy007
2

REFACTORING & TECHNICAL DEBT

Identify technical debt and plan incremental refactors with characterization tests.

Community
Advanced
oalansilvaoalansilva

tech-debt-portfolio

Catalog tech debt items, impacts, and dependencies to generate a prioritized roadmap.

Community
Intermediate
rodrigo-altissimorodrigo-altissimo

software-engineering-eng-tdd

Locate seams and break dependencies to make legacy code testable.

Community
Advanced
nikhillinitnikhillinit

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Community
Advanced