game-dev▌

### 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')"

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

### Regression Suite - name: regression-suite - description: "Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementi - argument-hint: "[update | audit | report]"

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

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

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

### Map Systems - description: "Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index." - argument-hint: "[next | system-name] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, AskUserQuestion, TodoWrite, Task

### Release Checklist - name: release-checklist - description: "Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness." - argument-hint: "[platform: pc|console|mobile|all]"

### Sprint Plan - description: "Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs - argument-hint: "[new|update|status] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion