# Available Skills (Slash Commands) 52 slash commands organized by phase. Type `/` in Claude Code to access any of them. ## Onboarding & Navigation | Command | Purpose | |---------|---------| | `/start` | First-time onboarding — asks where you are, then guides you to the right workflow | | `/help` | Context-aware "what do I do next?" — reads current stage and surfaces the required next step | | `/project-stage-detect` | Full project audit — detect phase, identify existence gaps, recommend next steps | | `/setup-engine` | Configure engine + version, detect knowledge gaps, populate version-aware reference docs | | `/adopt` | Brownfield format audit — checks internal structure of existing GDDs/ADRs/stories, produces migration plan | ## Game Design | Command | Purpose | |---------|---------| | `/brainstorm` | Guided ideation using professional studio methods (MDA, SDT, Bartle, verb-first) | | `/map-systems` | Decompose game concept into systems, map dependencies, prioritize design order | | `/design-system` | Guided, section-by-section GDD authoring for a single game system | | `/quick-design` | Lightweight design spec for small changes — tuning, tweaks, minor additions | | `/review-all-gdds` | Cross-GDD consistency and game design holism review across all design docs | | `/propagate-design-change` | When a GDD is revised, find affected ADRs and produce an impact report | ## UX & Interface Design | Command | Purpose | |---------|---------| | `/ux-design` | Guided section-by-section UX spec authoring (screen/flow, HUD, or pattern library) | | `/ux-review` | Validate UX specs for GDD alignment, accessibility, and pattern compliance | ## Architecture | Command | Purpose | |---------|---------| | `/create-architecture` | Guided authoring of the master architecture document | | `/architecture-decision` | Create an Architecture Decision Record (ADR) | | `/architecture-review` | Validate all ADRs for completeness, dependency ordering, and GDD coverage | | `/create-control-manifest` | Generate flat programmer rules sheet from accepted ADRs | ## Stories & Sprints | Command | Purpose | |---------|---------| | `/create-epics` | Translate GDDs + ADRs into epics — one per architectural module | | `/create-stories` | Break a single epic into implementable story files | | `/dev-story` | Read a story and implement it — routes to the correct programmer agent | | `/sprint-plan` | Generate or update a sprint plan; initializes sprint-status.yaml | | `/sprint-status` | Fast 30-line sprint snapshot (reads sprint-status.yaml) | | `/story-readiness` | Validate a story is implementation-ready before pickup (READY/NEEDS WORK/BLOCKED) | | `/story-done` | 8-phase completion review after implementation; updates story file, surfaces next story | | `/estimate` | Structured effort estimate with complexity, dependencies, and risk breakdown | ## Reviews & Analysis | Command | Purpose | |---------|---------| | `/design-review` | Review a game design document for completeness and consistency | | `/code-review` | Architectural code review for a file or changeset | | `/balance-check` | Analyze game balance data, formulas, and config — flag outliers | | `/asset-audit` | Audit assets for naming conventions, file size budgets, and pipeline compliance | | `/content-audit` | Audit GDD-specified content counts against implemented content | | `/scope-check` | Analyze feature or sprint scope against original plan, flag scope creep | | `/perf-profile` | Structured performance profiling with bottleneck identification | | `/tech-debt` | Scan, track, prioritize, and report on technical debt | | `/gate-check` | Validate readiness to advance between development phases (PASS/CONCERNS/FAIL) | ## Production | Command | Purpose | |---------|---------| | `/milestone-review` | Review milestone progress and generate status report | | `/retrospective` | Run a structured sprint or milestone retrospective | | `/bug-report` | Create a structured bug report | | `/reverse-document` | Generate design or architecture docs from existing implementation | | `/playtest-report` | Generate a structured playtest report or analyze existing playtest notes | ## Release | Command | Purpose | |---------|---------| | `/release-checklist` | Generate and validate a pre-release checklist for the current build | | `/launch-checklist` | Complete launch readiness validation across all departments | | `/changelog` | Auto-generate changelog from git commits and sprint data | | `/patch-notes` | Generate player-facing patch notes from git history and internal data | | `/hotfix` | Emergency fix workflow with audit trail, bypassing normal sprint process | ## Creative & Content | Command | Purpose | |---------|---------| | `/prototype` | Rapid throwaway prototype to validate a mechanic (relaxed standards, isolated worktree) | | `/onboard` | Generate contextual onboarding document for a new contributor or agent | | `/localize` | Localization workflow: string extraction, validation, translation readiness | ## Team Orchestration Coordinate multiple agents on a single feature area: | Command | Coordinates | |---------|-------------| | `/team-combat` | game-designer + gameplay-programmer + ai-programmer + technical-artist + sound-designer + qa-tester | | `/team-narrative` | narrative-director + writer + world-builder + level-designer | | `/team-ui` | ux-designer + ui-programmer + art-director + accessibility-specialist | | `/team-release` | release-manager + qa-lead + devops-engineer + producer | | `/team-polish` | performance-analyst + technical-artist + sound-designer + qa-tester | | `/team-audio` | audio-director + sound-designer + technical-artist + gameplay-programmer | | `/team-level` | level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester |