tech-debt-review

Read RALPH.md tech debt entries and generate a structured health summary.

Updated Mar 17, 2026

Search Tags:#review #assessment #sprint #risk #project-management #tech-debt #debt-health

Ready to run

npx skills add https://github.com/YarikChekin/ralph-cc --skill tech-debt-review-yarikchekin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt-review
Source: https://github.com/YarikChekin/ralph-cc/tree/main/skills/tech-debt-review
Command: npx skills add https://github.com/YarikChekin/ralph-cc --skill tech-debt-review-yarikchekin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tech debt accumulates silently, slowing delivery and increasing risk. This Skill reviews the designated tech debt file at key milestones and provides actionable recommendations to keep the codebase healthy.

Core Features & Use Cases

Reads a central tech debt file and aggregates active items, aging risk, and severities.
Applies thresholds to flag debt health and recommends next steps (immediate fixes, sprint backlog, or documentation).
Generates a concise summary suitable for product & engineering reviews.

Quick Start

Run /tech-debt-review to generate a live debt assessment for your current sprint.

Frequently Asked Questions about tech-debt-review

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

FAQPage Schema

How do I assess tech debt before a sprint starts?▼

Assess tech debt before a sprint by reading a centralized debt file to aggregate active items, evaluate aging risk, and flag high-severity issues. This generates a structured health summary with actionable recommendations for backlog prioritization.

What is the best way to track aging technical debt in project management?▼

Track aging technical debt by evaluating a central debt file at key milestones to aggregate active items and apply severity thresholds. This process flags growing risks and recommends scheduling immediate fixes, adding items to the sprint backlog, or documenting them.

How do I prioritize tech debt items during a project review?▼

Prioritize tech debt items during a project review by applying severity thresholds to aggregated entries from your debt file. This identifies high-severity and aging items, recommending immediate fixes for critical risks and sprint backlog inclusion for less urgent debt.

Do I need a specific file format to manage tech debt health?▼

Yes, managing tech debt health requires a centralized debt file located by reading RALPH.md to find Documents.tech_debt. This file stores active items, allowing the review process to count entries, evaluate severities, and present structured recommendations.

When should I review technical debt to minimize project risk?▼

Review technical debt to minimize project risk at sprint starts, before code merges, or during project reviews. Evaluating debt at these milestones catches accumulating issues early, applying health thresholds to recommend immediate fixes and prevent delivery slowdowns.