What problem does it solve? Developer agents often fail due to missing context: wrong libraries, wrong file locations, broken regressions, and vague requirements. This Skill creates a complete, self-contained story file that gives the dev agent everything needed for implementation, drawing from epics, PRD, architecture, UX docs, previous stories, and git history. ## Core Features & Use Cases - Story Auto-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 Gathering: Loads epics, architecture, UX, and previous story learnings via a discover-inputs protocol with sharded and whole-file strategies. - Quality Validation: Validates the generated story against a checklist that hunts for missing requirements, regression risks, and LLM-optimization issues before finalizing. - Use Case: A team using the BMad method runs this workflow to turn a backlog epic entry into a ready-for-dev story file with acceptance criteria, architecture guardrails, and testing requirements, then hands it to a dev-story agent. ## Quick Start Ask the agent to create the next story from the sprint backlog, or specify an epic-story number such as 2-4 to generate that story file. Note: this Skill is deprecated in favor of bmad-build and should only be used when explicitly invoked by name.
