What problem does it solve? Developers often receive vague or incomplete story requirements, leading to wrong libraries, broken regressions, and missed acceptance criteria. This Skill creates a comprehensive story file that gives the dev agent every piece of context needed for correct 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 Extraction: Analyzes epics, GDD, architecture, UX documents, project-context.md, previous story learnings, and git history to build developer guardrails. - Quality Validation: Validates the generated story against a checklist that hunts for missing requirements, vague instructions, and LLM-optimization issues before marking it ready-for-dev. - Use Case: A game development team finishes sprint planning and asks the agent to "create the next story"; the Skill produces a fully-contextualized story file with acceptance criteria, architecture compliance rules, and testing requirements, then 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" to generate a complete implementation-ready story file.
