What problem does it solve? Developer agents often fail because stories lack context: they reinvent existing code, use wrong libraries, break regressions, or ignore architecture constraints. This Skill creates a complete, self-contained 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 identifier like "2-4". - Exhaustive Context Gathering: Analyzes epics, PRD, architecture, UX documents, previous story learnings, and git history to extract technical requirements and guardrails. - Quality Validation: Runs a checklist-based review to catch missing requirements, vague acceptance criteria, and LLM-optimization issues before marking the story ready-for-dev. - Use Case: A team using the BMad method finishes sprint planning, then asks the agent to create the next story; the Skill produces a story file with acceptance criteria, architecture compliance notes, file structure requirements, and testing standards, and updates sprint status automatically. ## 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 fully contextualized implementation file.
