Gap closure: feedback loops, traceability, and new /content-audit skill

- NEW /content-audit skill: GDD-specified content vs implemented content gap
  report with COMPLETE/IN PROGRESS/EARLY/NOT STARTED per system
- balance-check: Fix & Verify Cycle phase (fix → re-verify → propagate-design-change)
- perf-profile: Scope & Timeline Decision phase for M/L effort optimizations
- playtest-report: Action Routing phase categorizes findings → design/balance/bugs/polish
- review-all-gdds: Phase 4 Cross-System Scenario Walkthrough (multi-system sequences)
- story-done: Test-Criterion Traceability (each AC mapped to a test, BLOCKING if >50% untested)
- code-review: ADR Compliance Check (ARCHITECTURAL VIOLATION / ADR DRIFT / MINOR DEVIATION)
- setup-engine: upgrade subcommand (pre-upgrade API scan, migration plan, VERSION.md update)
- story-readiness: Asset References Check (verifies referenced asset paths exist)
- validate-assets.sh: invalid JSON now exits 1 (blocking); naming issues exit 0 (warning)
- workflow-catalog.yaml + sprint-plan: /scope-check wired into production phase

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.claude/skills/playtest-report/SKILL.md

@@ -75,3 +75,35 @@ When invoked with `new`, generate this template:
 When invoked with `analyze`, read the raw notes, cross-reference with existing
 design documents, and fill in the template above with structured findings.
 Flag any playtest observations that conflict with design intent.
+
+After generating or analyzing a report, run the **Action Routing** phase:
+
+**Action Routing**
+
+Categorize all findings from the report into the four buckets below (a single
+finding may appear in more than one bucket if appropriate):
+
+- **Design changes needed** — fun issues, player confusion, broken mechanics,
+  observations that conflict with the GDD's intended experience
+- **Balance adjustments** — numbers feel wrong, difficulty too spiked or too
+  flat, economy or progression feedback
+- **Bug reports** — clear implementation defects that are reproducible
+- **Polish items** — not blocking progress, but friction or feel issues noted
+  for later
+
+Present the categorized list, then provide the routing guidance for each
+non-empty bucket:
+
+- **Design changes:** "These findings suggest GDD revisions. Run
+  `/propagate-design-change [path]` on the affected design document to find
+  downstream impacts before making changes."
+- **Balance adjustments:** "Run `/balance-check [system]` to verify the full
+  balance picture before tuning individual values."
+- **Bugs:** "Use `/bug-report` to formally track these so they are not lost
+  between sessions."
+- **Polish items:** "No immediate action required. Consider adding these to the
+  polish backlog in `production/` when the team reaches that phase."
+
+Finally, ask:
+
+> "Which category would you like to act on first?"