What problem does it solve? Writing implementation stories by hand often leaves developers without the architecture constraints, previous-story learnings, and project conventions they need, causing rework and regressions. 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 "1-2-user-auth". - Exhaustive context gathering: Loads epics, GDD, architecture, UX docs, project-context.md, previous story files, and recent git history to extract requirements and guardrails. - Quality validation: Validates the generated story against a checklist that hunts for missing requirements, wrong libraries, and regression risks before marking it ready-for-dev. - Use Case: A game development team finishes sprint planning and says "create the next story"; the Skill auto-selects the next backlog story, assembles all technical context, writes the story file, and updates sprint status to ready-for-dev. ## Quick Start Ask the agent to create the next story from the sprint backlog, or specify a story such as "create story 2-4".
