What problem does it solve? Implementing a game development story requires assembling scattered context — the story file, GDD requirement, governing ADR, and control manifest — and routing work to the right specialist. This Skill automates that orchestration so implementation follows architectural decisions instead of drifting from design. ## Core Features & Use Cases - Full Context Loading: Reads the story file, TR registry, governing ADR, control manifest, and engine preferences before any code is written, blocking on missing critical files. - Agent Routing: Selects the correct programmer agent (gameplay, UI, AI, network, engine) based on story layer, type, and engine, spawning engine specialists for high-risk stories. - Test Enforcement: Requires Logic and Integration stories to produce a test file at the path specified in the story's Test Evidence section, with one test per acceptance criterion. - Use Case: A team has a sprint of stories written against ADRs for a Godot 4 project. Run this Skill on each story to have the right specialist implement the code and tests, then hand off to code review and story closure. ## Quick Start Use $ai-game-studio:dev-story with the path to a ready story file to implement it with full architectural context.
