Donchitos/Claude-Code-Game-Studios

adopt

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

architecture-decision

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

architecture-review

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

art-bible

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

asset-audit

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

asset-spec

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

balance-check

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

brainstorm

Guided concept ideation using professional studio techniques, player psychology, creative exploration.

bug-report

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

bug-triage

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

changelog

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

code-review

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

consistency-check

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

content-audit

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

create-architecture

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

create-control-manifest

Flat must-do/never-do rules sheet per system and layer, extracted from Accepted ADRs. ADRs explain why; this is actionable.

create-epics

Turn GDDs plus architecture into epics — one per architectural module, with untraced requirements. Then /create-stories [epic-slug].

create-stories

Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria. Reads the control manifest. After /create-epics.

day-one-patch

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

design-review

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

design-system

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

dev-story

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

estimate

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

gate-check

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

help

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

hotfix

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

launch-checklist

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

localize

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

map-systems

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

milestone-review

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

onboard

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

patch-notes

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

perf-profile

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

playtest-report

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

project-stage-detect

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

propagate-design-change

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

prototype

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

qa-plan

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

quick-design

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

regression-suite

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