What problem does it solve? Development agents often fail because story files lack the technical context needed for correct implementation, leading to reinvented wheels, wrong libraries, and broken regressions. This Skill creates fully-contextualized story files that give the dev agent everything required for accurate implementation. ## Core Features & Use Cases - Automated 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 Gathering: Loads epics, PRD, architecture, and UX documents (whole or sharded) plus previous story learnings and git history to build complete developer guidance. - Quality Validation Checklist: Validates the generated story against a competitive review checklist that catches critical omissions, enhancement opportunities, and LLM-optimization issues before marking the story ready-for-dev. - Use Case: A team using the BMAD method runs sprint planning, then asks the agent to create the next story; the Skill produces a story file with acceptance criteria, architecture guardrails, library versions, and testing requirements, 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-1" to generate a ready-for-dev story file.
