tech-debt

Score technical debt across architecture, testing, documentation, and infrastructure.

3|Updated Mar 18, 2026

Search Tags:#testing #architecture #documentation #infrastructure #analyze #technical-debt #scorecard

Ready to run

npx skills add https://github.com/rshade/agent-skills --skill tech-debt-rshade

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/rshade/agent-skills/tree/main/skills/tech-debt
Command: npx skills add https://github.com/rshade/agent-skills --skill tech-debt-rshade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic technical debt analysis across architecture, testing, documentation, and infrastructure. Investigates the codebase, scores findings by impact and effort, and generates a prioritized TECH_DEBT.md remediation plan. Delegates to specialized skills for code quality (scout) and linting (lint-fix). Use when assessing overall project health, planning cleanup sprints, or onboarding to an unfamiliar codebase.

Core Features & Use Cases

Systematically gather context and scores across eight categories to quantify debt
Delegate specialized checks to scout and lint-fix for code quality and linting, plus other delegated areas
Generate a TECH_DEBT.md remediation plan with an executable scorecard and remediation roadmap

Quick Start

Run the tech-debt skill against your project repository to produce a prioritized remediation plan.

Frequently Asked Questions about tech-debt

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

FAQPage Schema

How do I assess technical debt across architecture, testing, and infrastructure?▼

To assess technical debt, investigate the codebase and score findings by impact and effort across architecture, testing, documentation, and infrastructure. This systematic analysis produces a prioritized remediation plan for your project.

What is the best way to generate a technical debt scorecard for an unfamiliar codebase?▼

The best way to generate a technical debt scorecard for an unfamiliar codebase is to run an analysis that applies linting, test suite, and CI configuration checks. It outputs a comprehensive scorecard with an executive summary and remediation roadmap.

How do I create a prioritized cleanup plan for technical debt?▼

You create a prioritized cleanup plan for technical debt by scoring findings across eight categories and generating a TECH_DEBT.md report. This report includes an executable scorecard and a structured remediation roadmap to guide cleanup sprints.

Does technical debt analysis work with projects that have CI configurations and linting?▼

Yes, technical debt analysis works with projects that have CI configurations, linting, and test suites. It applies the analysis directly to these project configurations to gather context and produce a comprehensive scorecard.

Can I use code quality and linting checks for my technical debt analysis?▼

You can use code quality and linting checks for technical debt analysis by delegating specialized checks to dedicated tools. This delegation gathers code quality and linting context alongside architecture, testing, documentation, and infrastructure scoring.

What does a technical debt remediation report include?▼

A technical debt remediation report includes an executive summary, a comprehensive scorecard, and a remediation roadmap. It categorizes findings across eight areas to provide a structured workflow for project health assessment and cleanup sprint planning.