claude▌

### Story Done - description: "End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story sta - argument-hint: "[story-file-path] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Bash, Edit, AskUserQuestion, Task

### Team Combat - description: "Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat fe - argument-hint: "[combat feature description]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Playtest Report - name: playtest-report - description: "Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis." - argument-hint: "[new|analyze path-to-notes] [--review full|lean|solo]"

### Security Audit - description: "Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with remedi - argument-hint: "[full | network | save | input | quick]" - allowed-tools: Read, Glob, Grep, Bash, Write, Task

### Team Audio - description: "Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation." - argument-hint: "[feature or area to design audio for]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### Team Polish - description: "Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality." - argument-hint: "[feature or area to polish]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite

### 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

### Smoke Check - description: "Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories ar - argument-hint: "[sprint | quick | --platform pc|console|mobile|all]" - allowed-tools: Read, Glob, Grep, Bash, Write, AskUserQuestion

### Quick Design - description: "Lightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too small to w - argument-hint: "[brief description of the change]" - allowed-tools: Read, Glob, Grep, Write, Edit

### Sprint Status - description: "Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any ti - argument-hint: "[sprint-number or blank for current]" - allowed-tools: Read, Glob, Grep