claude▌

### Retrospective - description: "Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration." - argument-hint: "[sprint-N|milestone-name]" - allowed-tools: Read, Glob, Grep, Write

### Gate Check - description: "Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to - argument-hint: "[target-phase: systems-design | technical-setup | pre-production | production | polish | release] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Bash, Write, Task, AskUserQuestion

### Prototype - description: "Rapid prototyping workflow. Skips normal standards to quickly validate a game concept or mechanic. Produces throwaway code and a structured prototype report." - argument-hint: "[concept-description] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task

### Milestone Review - name: milestone-review - description: "Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when ev - argument-hint: "[milestone-name|current] [--review full|lean|solo]"

### Launch Checklist - name: launch-checklist - description: "Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs." - argument-hint: "[launch-date or 'dry-run']"

### Reverse Document - name: reverse-document - description: "Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs." - argument-hint: "<type> <path> (e.g., 'design src/gameplay/combat' or 'architecture src/core')"

### Start - description: "First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions." - argument-hint: "[no arguments]" - allowed-tools: Read, Glob, Grep, Write, AskUserQuestion

### Propagate Design Change - name: propagate-design-change - description: "When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user - argument-hint: "[path/to/changed-gdd.md]"

### Onboard - description: "Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the - argument-hint: "[role|area]" - allowed-tools: Read, Glob, Grep, Write

### Design System - description: "Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, - argument-hint: "<system-name> [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion, TodoWrite