Release v0.4.0: UX pipeline, game-dev improvements

## New Skills (9)
- /quick-design: lightweight spec path for small changes (bypasses full GDD pipeline)
- /story-readiness: validates stories are implementation-ready before pickup
- /story-done: end-of-story completion review (criteria verification, deviation check, status update)
- /sprint-status: fast 30-line sprint snapshot, read-only
- /ux-design: guided section-by-section UX spec authoring (screen/flow/HUD/patterns)
- /ux-review: UX spec validation with APPROVED/NEEDS REVISION/MAJOR REVISION verdict
- /architecture-review, /create-architecture, /create-control-manifest,
  /create-epics-stories, /propagate-design-change, /review-all-gdds (pipeline completion)

## New Templates (7)
- player-journey.md: 6-phase emotional arc, critical moments, retention hooks
- difficulty-curve.md: difficulty axes, onboarding ramp, cross-system interactions
- ux-spec.md: per-screen UX spec with states, interaction map, data requirements, events
- hud-design.md: whole-game HUD with philosophy, info architecture, element specs
- accessibility-requirements.md: project-wide accessibility tier commitment and audit
- interaction-pattern-library.md: 26 standard + game-specific patterns with full state specs
- architecture-traceability.md: GDD requirements to ADR coverage matrix

## Updated Skills & Templates
- gate-check: Vertical Slice hard gate, playtesting strengthened, UX artifacts required
- team-ui: full UX pipeline integration (/ux-design + /ux-review + accessibility-specialist)
- game-design-document: Game Feel section (input latency, animation frames, impact moments)
- implementation-agent-protocol: /story-done as explicit final step of every story
- architecture-decision, design-system: pipeline completion updates

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

.claude/docs/templates/collaborative-protocols/implementation-agent-protocol.md

@@ -40,10 +40,11 @@ Before writing any code:
    - For multi-file changes, list all affected files
    - Wait for "yes" before using Write/Edit tools
 
-6. **Offer next steps:**
-   - "Should I write tests now, or would you like to review the implementation first?"
-   - "This is ready for /code-review if you'd like validation"
-   - "I notice [potential improvement]. Should I refactor, or is this good for now?"
+6. **Complete the story with `/story-done`:**
+   - When implementation (and tests, if written) is complete, invoke `/story-done [story-file-path]`
+   - This verifies acceptance criteria, checks for GDD/ADR deviations, prompts code review, and updates the story status
+   - Do NOT mark a story complete manually — always go through `/story-done`
+   - If no story file exists for this work (ad-hoc task), offer `/code-review` directly instead
 
 #### Example Interaction Pattern
 
@@ -109,7 +110,11 @@ User: "A, write tests"
 
 You: [creates tests/combat/test_damage_calculator.gd]
      "Created test file with 6 test cases covering the acceptance criteria from the design doc.
-      All tests passing. Ready to commit?"
+      All tests passing.
+
+      Running /story-done to verify acceptance criteria and close out the story."
+
+[/story-done runs — verifies criteria, checks deviations, prompts code review, updates story status]
 ```
 
 #### Collaborative Mindset
@@ -120,6 +125,7 @@ You: [creates tests/combat/test_damage_calculator.gd]
 - Flag deviations from design docs explicitly — designer should know if implementation differs
 - Rules are your friend — when they flag issues, they're usually right
 - Tests prove it works — offer to write them proactively
+- Story completion is explicit — use `/story-done` to close every story, never assume done because code is written
 
 #### Structured Decision UI