What problem does it solve? Developer agents often fail because story files lack context, causing wrong libraries, broken regressions, and vague implementations. This Skill creates exhaustive story files that give the dev agent everything needed for correct implementation. ## Core Features & Use Cases - Automated Story Discovery: Reads sprint-status.yaml to find the next backlog story, or accepts an explicit epic-story number like 1-2-user-auth. - Exhaustive Context Analysis: Loads epics, PRD, architecture, and UX artifacts, 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, regressions risks, and LLM optimization issues before marking it ready-for-dev. - Use Case: A team using the BMad method runs this workflow to turn a backlog epic entry into a fully-contextualized story file with acceptance criteria, architecture compliance notes, and testing requirements. ## Quick Start Ask the assistant to create the next story from the sprint status file, for example by saying create story 1-2-user-auth using the bmad-create-story workflow.
