What problem does it solve? Writing implementation stories by hand often leaves developers without the architecture constraints, previous-story learnings, and technical specifics they need, causing wrong libraries, regressions, and rework. This Skill automates the creation of a complete, context-rich story file so the dev agent has everything required for implementation. ## Core Features & Use Cases - Automatic Story Discovery: Reads sprint-status.yaml to find the next backlog story, or accepts an explicit epic-story identifier like "2-4". - Exhaustive Context Analysis: Loads epics, GDD, architecture, UX documents, project-context.md, previous story files, and git history to extract requirements and guardrails. - Structured Story Generation: Produces a story file from a template with acceptance criteria, dev notes, architecture compliance rules, and testing requirements, then updates sprint status to ready-for-dev. - Quality Validation: Runs a checklist-based review to catch missing requirements, vague instructions, and disaster risks before finalizing. - Use Case: A game development team finishes sprint planning and asks the agent to "create the next story"; the Skill analyzes all planning artifacts and outputs a ready-for-dev story file the dev agent can implement directly. ## Quick Start Ask the agent to create the next story from the sprint backlog, or specify a story such as "create story 2-4" to generate its implementation file.
