What problem does it solve? Development agents often fail because stories lack context: wrong libraries, wrong file locations, broken regressions, and vague acceptance criteria. This Skill creates a comprehensive story file that gives the dev agent everything needed for correct implementation, preventing common LLM developer mistakes. ## 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 Analysis: Loads and analyzes epics, PRD, architecture, and UX documents plus previous story learnings and git history to build complete developer guardrails. - Quality Validation: Validates the generated story against a checklist that hunts for missing requirements, regression risks, and LLM-optimization issues before finalizing. - Use Case: After sprint planning, ask the agent to create the next story; it auto-selects the first backlog story, analyzes all planning artifacts, and writes a ready-for-dev story file with architecture compliance rules, testing requirements, and file structure guidance. ## Quick Start Ask the agent to create the next story from the sprint backlog, for example by saying "create the next story" or "create story 1-2-user-auth".