Claude-Code-Game-Studios

Brownfield audit — do existing artifacts actually work? Numbered migration plan. Unlike /project-stage-detect, checks compliance not existence.

Create an ADR documenting a technical decision: context, alternatives considered, consequences.

Traceability matrix mapping GDD requirements to ADRs. Finds gaps, cross-ADR conflicts, engine compatibility. PASS/CONCERNS/NOT ASSESSED/FAIL.

Author the Art Bible — visual identity gating asset production. Run before /map-systems.

Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.

Per-asset visual specs plus AI generation prompts from GDDs and character profiles. After the art bible.

Find balance outliers, broken progressions, degenerate strategies, economy imbalances in formulas and data. 'Check game balance'.

Guides the user through finding and choosing a game concept. Use when the user wants game ideas, a new concept, a game jam idea, or to explore other directions, including dropping the current idea and starting over.

Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.

Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.

Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.

Architectural code review — coding standards, SOLID, testability, performance concerns.

Scan GDDs against the entity registry for cross-document conflicts. Grep-first approach targets conflicting sections, different stats.

Audit GDD content counts against what's implemented — planned vs built.

Author the architecture blueprint before code is written. Validates decisions against the pinned engine, flags knowledge gaps.

Builds a short list of must-do and never-do coding rules per system from accepted ADRs. Use when the user wants programmer rules or a cheat sheet from the ADRs, or needs it regenerated after ADR changes.

Turns the GDDs and architecture into epics, one per architectural module. Use when the user wants to break the game into epics or plan the work before writing stories. Not for splitting one epic into stories.

Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.

Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.

Reviews one design document for completeness, internal consistency, implementability, and design standards. Before handing to programmers.