Claude-Code-Game-Studios

Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.

Sprint or milestone retrospective from completed work, velocity, blockers. Actionable insights for the next iteration.

Generate missing design or architecture docs from existing implementation — works backwards from code and prototypes.

Holistic cross-GDD review — contradictions between systems, dominant strategies, economic imbalance, cognitive overload, pillar drift.

Scope creep check — current scope versus the original plan. Flags additions, quantifies bloat, recommends cuts. 'Any scope creep?'

Security audit — save tampering, cheat vectors, network exploits, data exposure, input validation. Before public or multiplayer release.

View or change project config — effective merged values, or set locally in project.local.yaml.

Configure engine and version. Pins it in CLAUDE.md; WebSearch fills reference docs when the version is beyond LLM training data.

Improve a skill via a test-fix-retest loop — static checks, targeted fixes, keep or revert on score change.

Validate skill files for structural compliance and behavioral correctness. Four modes: static linter, spec, category rubric, audit.

Critical-path smoke gate before QA hand-off — runs the automated suite. A failed check means the build is not QA-ready.

Soak test protocol for extended play — what to observe and log for slow leaks, fatigue, late-appearing edge cases.

New or updated sprint plan from the current milestone, completed work, and available capacity.

Fast, concise sprint snapshot — burndown and emerging risks for situational awareness. 'How is the sprint going?'

First-time onboarding — asks where you are, then guides you to the right workflow.

End-of-story completion review — verifies each acceptance criterion, checks GDD/ADR deviations, prompts code review, updates status.

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Orchestrate the audio team — audio-director, sound-designer, technical-artist, gameplay-programmer — direction through implementation.

Orchestrate the combat team — game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, qa-tester — design through implement and validate.

Orchestrate the level team — level-designer, narrative-director, world-builder, art-director, systems-designer, qa-tester — for complete area creation.