What problem does it solve? Implementing a game development story requires assembling scattered context — the story file, GDD requirements, architecture decision records, and control manifest rules — and routing it to the right specialist. This Skill automates that assembly and routing so implementation follows the governing ADR 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 implementation if required files are missing. - Agent Routing: Selects the correct programmer agent (gameplay, UI, AI, network, engine) based on the story's layer, type, and engine, spawning engine specialists for high-risk stories. - Test Evidence Enforcement: Requires Logic and Integration stories to ship with a test file covering every acceptance criterion before the story can close. - Use Case: A team working in Godot 4 has a sprint of stories under production/epics/. Running this Skill on a story validates dependencies, checks manifest version drift, spawns the right programmer and Godot specialist, and produces source code plus a test file with a structured implementation summary. ## Quick Start Use the dev-story skill to implement the story at production/epics/combat/story-03.md following its governing ADR.
