Technical Debt Analysis

Investigate the codebase across 8 categories, score each finding by impact and effort, and generate a prioritized TECH_DEBT.md remediation plan. Four categories are analyzed directly; four delegate to specialized skills.

Prerequisite check

git --version 2>/dev/null && git rev-parse --is-inside-work-tree 2>/dev/null

If not in a git repository, warn but proceed — git history analysis will be unavailable but other checks still work.

Step 1: Project context