What problem does it solve? Development agents often fail because story files lack the context needed for correct implementation, leading to reinvented wheels, wrong libraries, broken regressions, and vague implementations. This Skill creates exhaustive 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 Extraction: Analyzes epics, PRD, architecture, and UX documents 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 before handoff to the dev agent. - Use Case: A team using the BMad method asks the agent to "create the next story"; the Skill locates the next backlog story, mines all planning artifacts, and writes a ready-for-dev story file with architecture compliance rules, testing requirements, and file structure constraints. ## 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.
