Release v0.4.0: /consistency-check, skill fixes, genre-agnostic agents

New skill: /consistency-check — cross-GDD entity registry scanner
New registries: design/registry/entities.yaml, docs/registry/architecture.yaml
Skill fixes: no-arg guards, verdict keywords, AskUserQuestion gates on all team-* skills
Agent fixes: genre-agnostic language in game-designer, systems-designer, economy-designer, live-ops-designer
Docs: skill/template counts corrected, stale references cleaned up

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

.claude/skills/patch-notes/SKILL.md

@@ -8,36 +8,47 @@ model: haiku
 agent: community-manager
 ---
 
-When this skill is invoked:
+## Phase 1: Parse Arguments
 
-1. **Parse the arguments**:
-   - `version`: the release version to generate notes for (e.g., `1.2.0`)
-   - `--style`: output style — `brief` (bullet points), `detailed` (with context),
-     `full` (with developer commentary). Default: `detailed`.
+- `version`: the release version to generate notes for (e.g., `1.2.0`)
+- `--style`: output style — `brief` (bullet points), `detailed` (with context), `full` (with developer commentary). Default: `detailed`.
 
-2. **Gather change data from multiple sources**:
-   - Read the internal changelog at `production/releases/[version]/changelog.md` if it exists
-   - Run `git log` between the previous release tag and current tag/HEAD
-   - Read sprint retrospectives in `production/sprints/` for context
-   - Read any balance change documents in `design/balance/`
-   - Read bug fix records from QA if available
+If no version is provided, ask the user before proceeding.
 
-3. **Categorize all changes** into player-facing categories:
-   - **New Content**: new features, maps, characters, items, modes
-   - **Gameplay Changes**: balance adjustments, mechanic changes, progression changes
-   - **Quality of Life**: UI improvements, convenience features, accessibility
-   - **Bug Fixes**: grouped by system (combat, UI, networking, etc.)
-   - **Performance**: optimization improvements players might notice
-   - **Known Issues**: transparency about unresolved problems
+---
 
-4. **Translate developer language to player language**:
-   - "Refactored damage calculation pipeline" → "Improved hit detection accuracy"
-   - "Fixed null reference in inventory manager" → "Fixed a crash when opening inventory"
-   - "Reduced GC allocations in combat loop" → "Improved combat performance"
-   - Remove purely internal changes that don't affect players
-   - Preserve specific numbers for balance changes (damage: 50 → 45)
+## Phase 2: Gather Change Data
 
-5. **Generate the patch notes** using the appropriate style:
+- Read the internal changelog at `production/releases/[version]/changelog.md` if it exists
+- Run `git log` between the previous release tag and current tag/HEAD
+- Read sprint retrospectives in `production/sprints/` for context
+- Read any balance change documents in `design/balance/`
+- Read bug fix records from QA if available
+
+---
+
+## Phase 3: Categorize and Translate
+
+Categorize all changes into player-facing categories:
+
+- **New Content**: new features, maps, characters, items, modes
+- **Gameplay Changes**: balance adjustments, mechanic changes, progression changes
+- **Quality of Life**: UI improvements, convenience features, accessibility
+- **Bug Fixes**: grouped by system (combat, UI, networking, etc.)
+- **Performance**: optimization improvements players might notice
+- **Known Issues**: transparency about unresolved problems
+
+Translate developer language to player language:
+
+- "Refactored damage calculation pipeline" → "Improved hit detection accuracy"
+- "Fixed null reference in inventory manager" → "Fixed a crash when opening inventory"
+- "Reduced GC allocations in combat loop" → "Improved combat performance"
+- Remove purely internal changes that don't affect players
+- Preserve specific numbers for balance changes (damage: 50 → 45)
+
+---
+
+## Phase 4: Generate Patch Notes
 
 ### Brief Style
 ```markdown
@@ -108,15 +119,33 @@ Includes everything from Detailed, plus:
 > what the team learned. Written in first-person team voice.]
 ```
 
-6. **Review the output** for:
-   - No internal jargon (replace technical terms with player-friendly language)
-   - No references to internal systems, tickets, or sprint numbers
-   - Balance changes include before/after values
-   - Bug fixes describe the player experience, not the technical cause
-   - Tone matches the game's voice (adjust formality based on game style)
+---
 
-7. **Save the patch notes** to `production/releases/[version]/patch-notes.md`,
-   creating the directory if needed.
+## Phase 5: Review Output
 
-8. **Output to the user**: the complete patch notes, the file path, a count of
-   changes by category, and any internal changes that were excluded (for review).
+Check the generated notes for:
+
+- No internal jargon (replace technical terms with player-friendly language)
+- No references to internal systems, tickets, or sprint numbers
+- Balance changes include before/after values
+- Bug fixes describe the player experience, not the technical cause
+- Tone matches the game's voice (adjust formality based on game style)
+
+---
+
+## Phase 6: Save Patch Notes
+
+Present the completed patch notes to the user along with: a count of changes by category, and any internal changes that were excluded (for review).
+
+Ask: "May I write this to `production/releases/[version]/patch-notes.md`?"
+
+If yes, write the file, creating the directory if needed.
+
+---
+
+## Phase 7: Next Steps
+
+Verdict: **COMPLETE** — patch notes generated and saved.
+
+- Run `/release-checklist` to verify all other release gates are met before publishing.
+- Share the patch notes draft with the community-manager for tone review before posting publicly.