Explicit tech debt list maintained

Severity: Critical

Technical debt must be explicitly tracked, not just "known" by the team. Without visibility, debt compounds invisibly and prioritization becomes impossible.

Check automatically:

# Look for tech debt documentation
find . -maxdepth 4 -type f \( -name "*debt*" -o -name "*backlog*" -o -name "*technical*" \) -name "*.md" 2>/dev/null | grep -v node_modules

# Search for debt tracking content
grep -riE "tech(nical)? debt|refactor|legacy|cleanup" docs/ README.md --include="*.md" 2>/dev/null

# Check for debt label in GitHub Issues
gh label list 2>/dev/null | grep -iE "debt|refactor|tech"

# Count open debt items if label exists
gh issue list --label "tech-debt" --state open --json title --limit 100 2>/dev/null | jq length

Ask user:

• "Where does the team track technical debt?" (Linear, Jira, Notion, GitHub Issues, dedicated doc)
• "Is it a living list that gets updated?"
• "When was the last item added or resolved?"

Pass criteria:

• Dedicated tech debt tracking exists (board, label, document)
• Actively maintained (updated within last quarter)
• Discoverable by team members
• Contains actual items (not empty)

Fail criteria:

• No explicit tracking ("we just know")
• List exists but stale (last updated 6+ months ago)
• Scattered across random places with no central view
• Empty or abandoned tracking system

Evidence to capture:

• Location of debt tracking (URL, file path)
• Tracking method (label, board, document)
• Number of open items
• Last activity date

---