Claude-Code-Game-Studios

Section-by-section GDD authoring for one system — walks through each required section, cross-references dependencies.

Implement a story: ADR guidelines, right programmer agent, code plus test. Then /story-done (/story-readiness before, /code-review after, at standard/full).

Estimate task effort from complexity, dependencies, velocity, risk. Structured estimate with confidence levels.

Ready to advance between development phases? PASS/CONCERNS/NOT ASSESSED/FAIL with blockers and required artifacts. 'Can we move to production?'

What should I do next? Use when stuck or you don't know what to do.

Emergency fix bypassing normal sprint process — hotfix branch, approvals tracked, backport verified, full audit trail.

Launch readiness across every department: code, content, store, marketing, community, infrastructure, legal, go/no-go sign-offs.

Localization pipeline — find hardcoded strings, extract string tables, cultural review, VO, RTL, enforce string freeze.

Decompose a concept into individual systems, map dependencies, prioritize design order, create the systems index.

Milestone progress review — completeness, quality metrics, risk, go/no-go recommendation. At checkpoints or before a deadline.

Onboarding doc for a new contributor or agent — project state, conventions, priorities relevant to the specified role.

Player-facing patch notes from git history and changelogs. Translates developer language into player communication.

Performance profiling — find bottlenecks, measure against budgets, produce ranked optimization recommendations.

Structured playtest report template, or turn existing playtest notes into structured feedback.

Analyze project state, detect stage, identify gaps, recommend next steps. 'Where are we in development?'

A GDD changed — scan ADRs and the traceability index for now-stale architectural decisions. Impact report, guides resolution.

Concept prototype before GDDs — throwaway HTML, Engine or Paper build, PROCEED/PIVOT/KILL/NOT ASSESSED. After /brainstorm and /setup-engine.

QA test plan for a sprint — classifies stories by Logic/Integration/Visual/UI, covers automated tests, manual cases, smoke scope.

Lightweight spec for small changes — tuning adjustments, minor mechanics. Embeds directly into stories; skips full GDD.

Map test coverage to GDD critical paths, find fixed bugs lacking regression tests, flag drift from new features.