tech-debt

# Tech Debt You are identifying and prioritizing technical debt using Draft's Context-Driven Development methodology. ## Red Flags - STOP if you're: - Reporting debt without reading the actual code - Categorizing everything as high priority (prioritization requires trade-offs) - Suggesting rewrites when incremental fixes suffice - Ignoring effort estimates (impact without effort is not actionable) - Making up file locations or code patterns - Reporting framework conventions as debt **Evidence-based. Prioritized. Actionable.** --- ## Pre-Check ### 0. Capture Git Context ```bash git branch --show-current # Current branch name git rev-parse --short HEAD # Current commit hash ``` ### 1. Load Draft Context Read and follow the base procedure in `core/shared/draft-context-loading.md`. **Tech-debt-specific context application:** - Use `draft/.ai-context.md` for architecture, module boundaries, known technical decisions - Use `draft/tech-stack.md` for framework versions, dependency age, accepted patterns - Use `draft/guardrails.md` for known conventions and anti-patterns (anti-patterns ARE debt indicators) - Use `draft/product.md` for business priorities (aligns debt prioritization with product goals) If `draft/` does not exist: **STOP** — "No Draft context found. Run `/draft:init` first. Tech debt analysis requires project context." --- ## Step 1: Parse Arguments | Invocation | Behavior | |------------|----------| | `/draft:tech-debt` | Full codebase tech debt sca...