Skills update: team-live-ops skill + improvements across 18 existing skills

- Add new /team-live-ops skill for post-launch content planning orchestration
- Expand setup-engine, code-review, create-epics-stories, prototype with additional context
- Enrich team-* skills (audio, combat, level, narrative, polish, release, ui) with new phases/agents
- Update architecture-decision and architecture-review with dependency ordering improvements
- Minor additions to balance-check, hotfix, localize, patch-notes, perf-profile
- Populate technical-preferences.md with structured configuration sections

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

.claude/skills/architecture-review/SKILL.md

@@ -3,7 +3,7 @@ name: architecture-review
 description: "Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review."
 argument-hint: "[focus: full | coverage | consistency | engine | single-gdd path/to/gdd.md]"
 user-invocable: true
-allowed-tools: Read, Glob, Grep, Write
+allowed-tools: Read, Glob, Grep, Write, Task
 context: fork
 agent: technical-director
 ---
@@ -237,6 +237,20 @@ Post-Cutoff API Conflicts:
 
 ---
 
+### Engine Specialist Consultation
+
+After completing the engine audit above, spawn the **primary engine specialist** via Task for a domain-expert second opinion:
+- Read `.claude/docs/technical-preferences.md` `Engine Specialists` section to get the primary specialist
+- If no engine is configured, skip this consultation
+- Spawn `subagent_type: [primary specialist]` with: all ADRs that contain engine-specific decisions or `Post-Cutoff APIs Used` fields, the engine reference docs, and the Phase 5 audit findings. Ask them to:
+  1. Confirm or challenge each audit finding — specialists may know of engine nuances not captured in the reference docs
+  2. Identify engine-specific anti-patterns in the ADRs that the audit may have missed (e.g., using the wrong Godot node type, Unity component coupling, Unreal subsystem misuse)
+  3. Flag ADRs that make assumptions about engine behaviour that differ from the actual pinned version
+
+Incorporate additional findings under `### Engine Specialist Findings` in the Phase 5 output. These feed into the final verdict — specialist-identified issues carry the same weight as audit-identified issues.
+
+---
+
 ## Phase 5b: Design Revision Flags (Architecture → GDD Feedback)
 
 For each **HIGH RISK engine finding** from Phase 5, check whether any GDD makes an