What problem does it solve? Developer agents often fail because stories lack context: wrong libraries, wrong file locations, broken regressions, and ignored UX requirements. This Skill creates a complete story file that gives the dev agent everything 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 number like 2-4. - Exhaustive Context Gathering: Analyzes epics, PRD, architecture, UX docs, previous story learnings, and recent git history to build developer guardrails. - Quality Validation: Runs a checklist-based review pass that identifies critical gaps and applies fixes before marking the story ready-for-dev. - Use Case: After sprint planning, ask for the next story and receive a fully-contextualized story file with acceptance criteria, architecture compliance notes, file structure requirements, and testing standards, with sprint status updated automatically. ## Quick Start Ask the agent to create the next story from the sprint backlog, or specify a story such as "create story 1-2-user-auth".
