game-dev▌

### Create Control Manifest - name: create-control-manifest - description: "After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted A - argument-hint: "[update — regenerate from current ADRs]"

### Estimate - description: "Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels." - argument-hint: "[task-description]" - allowed-tools: Read, Glob, Grep

### Design Review - description: "Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programme - argument-hint: "[path-to-design-doc] [--depth full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Edit, Task, AskUserQuestion

### Create Epics - description: "Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories - argument-hint: "[system-name | layer: foundation|core|feature|presentation | all] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion

### Create Stories - description: "Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance c - argument-hint: "[epic-slug | epic-path] [--review full|lean|solo]" - allowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion

### Content Audit - description: "Audit GDD-specified content counts against implemented content. Identifies what's planned vs built." - argument-hint: "[system-name | --summary | (no arg = full audit)]" - allowed-tools: Read, Glob, Grep, Write

### Create Architecture - name: create-architecture - description: "Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a com - argument-hint: "[focus-area: full | layers | data-flow | api-boundaries | adr-audit] [--review full|lean|solo]"

### Day One Patch - description: "Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately af - argument-hint: "[scope: known-bugs | cert-feedback | all]" - allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion

### Consistency Check - name: consistency-check - description: "Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variabl - argument-hint: "[full | since-last-review | entity:<name> | item:<name>]"

### Dev Story - description: "Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, imp - argument-hint: "[story-path]" - allowed-tools: Read, Glob, Grep, Write, Bash, Task, AskUserQuestion