What problem does it solve? Breaking a large game design epic into small, implementable stories is error-prone: requirements get lost, acceptance criteria become untestable, and traceability to design documents breaks down. This Skill automates that decomposition while preserving full traceability to GDD requirements, architecture decisions, and QA test cases. ## Core Features & Use Cases - Epic-to-Story Decomposition: Reads an epic, its GDD, governing ADRs, and the control manifest, then groups acceptance criteria into right-sized stories (2-4 hour sessions) classified by type (Logic, Integration, Visual/Feel, UI, Config/Data). - Traceability Embedding: Each story file embeds its TR-ID from the traceability registry, governing ADR guidance, control manifest rules, and a required test evidence path. - QA Gate Integration: Optionally spawns a qa-lead gate (QL-STORY-READY) to validate testability, and generates Given/When/Then test specs or manual verification steps per story. - Use Case: After running create-epics for a combat system, run this Skill to produce story-001 through story-NNN files under production/epics/combat/, each ready for story-readiness and dev-story implementation. ## Quick Start Run $ai-game-studio:create-stories combat to break the combat epic into implementable story files with acceptance criteria and QA test cases.
