eng-tech-debt

Catalog tech debt items, score business impact, and generate prioritized payoff plans.

Updated Apr 14, 2026

Search Tags:#planning #prioritization #code-quality #risk-management #software-engineering #tech-debt

Ready to run

npx skills add https://github.com/viditparashar96/second-brain-claude --skill eng-tech-debt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eng-tech-debt
Source: https://github.com/viditparashar96/second-brain-claude/tree/main/skills/eng-tech-debt
Command: npx skills add https://github.com/viditparashar96/second-brain-claude --skill eng-tech-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tech debt accumulates across projects, slowing delivery, increasing risk, and muddying roadmaps. This Skill provides structured cataloging, scoring, and prioritized payoff planning to keep systems maintainable and aligned with business goals.

Core Features & Use Cases

Catalog debt items with title, product, component, and type (design/code/dependency/infra/docs).
Score items on reliability risk, velocity impact, customer impact, security risk, and scaling blockers; compute a composite priority.
Generate payoff plans, auto-escalate blockers when they block strategic priorities, and save local docs for review.
Use for cross-product debt management and leadership reporting.

Quick Start

Use this skill to add a debt item, view prioritized items, and generate a leadership report.

Frequently Asked Questions about eng-tech-debt

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

FAQPage Schema

How do I prioritize and catalog technical debt across multiple codebases?▼

You can catalog technical debt items by title, product, and component type, then score them on reliability, velocity, security, and scaling to compute a composite priority for cross-codebase management.

What is the best way to generate a tech debt leadership report for product roadmaps?▼

Generate a leadership report by scoring cataloged tech debt items for business impact and velocity risk, producing prioritized payoff plans that align legacy issues with strategic product goals.

How does scoring tech debt for business impact and risk work?▼

Tech debt scoring evaluates items against reliability risk, velocity impact, customer impact, security risk, and scaling blockers to calculate a composite priority and determine escalation needs.

Can I use this for cross-product tech debt management and auto-escalation?▼

Yes, this approach supports cross-product debt management by auto-escalating blockers when they intersect with strategic priorities, logging activity to memory, and saving per-item metadata locally.

Do I need external dependencies to store tech debt metadata locally?▼

No external dependencies are required; the system stores debt metadata locally in the docs directory, saves per-item documentation, and logs activity directly to memory for review.

What types of technical debt can I document and prioritize using this method?▼

You can document and prioritize design, code, dependency, infrastructure, and documentation debt, assessing each type's risk and impact to generate structured payoff plans.