tech-debt

Identify, categorize, and prioritize technical debt across a codebase.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/FoundationForge/cowork-plugins --skill tech-debt-foundationforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/FoundationForge/cowork-plugins/tree/main/plugins/engineering/skills/tech-debt
Command: npx skills add https://github.com/FoundationForge/cowork-plugins --skill tech-debt-foundationforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers and product teams struggle to discover, categorize, and prioritize technical debt across code, architecture, tests, dependencies, documentation, and infrastructure; this Skill provides a structured audit and scoring framework to turn vague code quality concerns into an actionable backlog.

Core Features & Use Cases

  • Categorization: Classify debt into code, architecture, test, dependency, documentation, and infrastructure buckets to highlight root causes.
  • Prioritization Framework: Score items by impact, risk, and effort using the provided formula to produce a ranked remediation list.
  • Deliverables: Produce estimated effort, business justification, and a phased remediation plan suitable for inclusion in sprint planning or roadmaps.
  • Use Case: Run a debt audit before a major release to identify high-risk areas, estimate fixes, and plan incremental remediation alongside feature work.

Quick Start

Run a technical debt audit on the payments service and return a prioritized remediation plan with estimated effort and business justification.

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 prioritize technical debt across a codebase?

To identify and prioritize technical debt, categorize items into code, architecture, test, dependency, documentation, and infrastructure buckets. Score each item by impact, risk, and effort to produce a ranked remediation list for sprint planning.

What is the best way to assess code health and architecture debt before a major release?

Assess code health and architecture debt by running a structured engineering audit that surfaces high-risk areas. This process estimates fix efforts and generates a phased remediation plan to execute alongside feature work.

How do you categorize technical debt for a refactoring initiative?

Categorize technical debt for refactoring by classifying issues into code, architecture, test, dependency, documentation, and infrastructure buckets. This highlights root causes and provides business justifications for specific backlog items.

Can I generate a visual report of my technical debt audit?

Yes, you can generate a visual report of your technical debt audit. The process produces an interactive visual-explainer HTML recap that details the prioritized list, scores, and phased remediation steps.

Does technical debt prioritization work for sprint planning and roadmaps?

Technical debt prioritization works directly for sprint planning and roadmaps by scoring items on impact, risk, and effort. It outputs estimated effort, business justification, and a phased remediation plan suitable for incremental scheduling.