What problem does it solve?
Game development story implementation typically requires manually gathering scattered context from story files, GDD requirement registries, architecture decision records (ADRs), control manifests, and engine preference documents, then coordinating the correct specialist programmer and engine experts, writing tests, and tracking acceptance criteria. This process is time-consuming, error-prone, and often leads to implementation drift from design guidelines or missed acceptance criteria.
Core Features & Use Cases
- Full Context Validation & Loading: Automatically verifies the existence of all required context files (TR registry, governing ADR, control manifest) before implementation, blocking work if critical files are missing to prevent invalid implementation.
- Intelligent Agent Routing: Automatically selects the correct primary programmer agent (engine, UI, gameplay, AI, network, etc.) and engine-specific specialist based on the story's layer, type, and engine risk, ensuring the right expertise is applied.
- End-to-End Implementation & Testing: Drives code implementation that strictly follows ADR guidelines and control manifest rules, writes required automated tests for Logic and Integration stories, and generates a detailed implementation summary with acceptance criteria coverage and deviation tracking.
- Use Case: For a game development team using Claude Code with a structured sprint process, use this Skill after running
/story-readiness to automatically implement a new player ability feature, ensuring it adheres to the team's architecture decisions, passes all required tests, and stays within the story's defined scope.
Quick Start
Invoke the dev-story skill with the file path to your validated game development story to automatically load all required context, route to the correct specialist agents, implement the feature and required tests, and generate a complete implementation summary.
