What problem does it solve? Technical debt accumulates silently during development and code review, with no consistent way to classify severity, decide whether to fix or defer, or detect stale entries. This Skill provides a unified framework for registering, prioritizing, and lifecycle-managing every tech debt item in a single SQLite table. ## Core Features & Use Cases - Classification Framework: 6 debt categories (Structural, Code Quality, Test, Documentation, Dependency) x 5 severity levels (P0-P4) x 4 resolution decisions (FIXED, DEFERRED, ACCEPTED, WON'T FIX), with a Priority Score formula to drive triage decisions. - Automation Rules: 5-Minute Rule for mandatory inline quick fixes, Boy Scout sweep during dev-story, 4 stale-detection mechanisms, and a 5-layer automated triage pyramid for bulk debt cleanup. - CLI and MCP Integration: Write, query, resolve, and audit debts via upsert-debt.js CLI commands or the search_debt MCP tool, with production gate thresholds blocking story completion. - Use Case: During a code review, an agent finds a React key warning, computes its Priority Score, applies the 5-Minute Rule, fixes it inline, and records the resolution with upsert-debt.js so the debt never enters the registry as noise. ## Quick Start Ask the agent to search open tech debt for the current story's files and classify each item using the Priority Score formula before deciding to fix, defer, or accept it.
