11-tech-debt

Harvest upstream outputs into a prioritized tech debt register with remediation roadmap.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compiles a consolidated, prioritized tech debt register by harvesting findings from upstream outputs. It synthesizes issues identified across pipelines into a single, actionable view.

Core Features & Use Cases

  • Harvest findings from upstream outputs (05-components-*.md, 08-patterns.md, 09-dependencies.md, 10-blueprint.md) and deduplicate to a unified debt catalog.
  • Classify each debt item by category (code quality, test coverage, architecture, resilience, security, dependency, data model) and assign severity and estimated effort.
  • Produce a remediation roadmap with Quick Wins, Planned Work, and Strategic items, enabling governance and sprint planning.
  • Supports a pipeline flow where it runs after 10-blueprint and before 12-traceability, consolidating findings into one view.

Quick Start

Run this skill after upstream outputs are available to generate the consolidated tech debt register.

Frequently Asked Questions about 11-tech-debt

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

FAQPage Schema
How do I consolidate tech debt from multiple analysis reports?

To consolidate tech debt, harvest findings from upstream outputs like component and dependency reports, then deduplicate items into a unified catalog. This process synthesizes issues across pipelines into a single, actionable view for governance.

What is a tech debt register and how does it help with roadmap prioritization?

A tech debt register is a structured catalog of identified issues classified by category, severity, and estimated effort. It enables roadmap prioritization by organizing items into Quick Wins, Planned Work, and Strategic tasks for sprint planning.

How do I classify tech debt severity and effort for remediation planning?

Classify tech debt by assigning severity and estimated effort to each deduplicated item across categories like code quality, architecture, and security. This classification produces a remediation roadmap structured by Quick Wins and Strategic items.

Can I generate a traceable remediation roadmap from blueprint and dependency analyses?

Yes, you can generate a traceable remediation roadmap by harvesting findings from upstream outputs such as blueprints and dependency analyses. The output includes debt IDs, sources, blast radius, and recommended remediation for full traceability.

What's the best way to deduplicate technical debt items across pipeline outputs?

The best way to deduplicate technical debt items is to consolidate findings from at least four upstream outputs into a single debt catalog. This ensures duplicate issues are merged while preserving source traceability and blast radius metrics.

Does this tech debt consolidation require specific upstream pipeline outputs?

Tech debt consolidation requires upstream outputs like 05-components, 08-patterns, 09-dependencies, and 10-blueprint to be available. Running this skill after these outputs ensures a comprehensive, deduplicated debt register.