bmad-create-story

Creating implementation-ready stories from agile epics requires extracting full context from BMAD architecture and sprint artifacts. This Skill analyzes prior story learnings and PRDs to output a complete markdown file with technical guardrails, file targets, and testing guidance for development.

A ready-for-dev story file includes deep context extracted from epics, PRDs, architecture notes, and prior story learnings. It provides structured technical notes, testing guidance, file targets, and sprint status updates to ensure developers have exhaustive context without ambiguity.

Adding technical guardrails to agile story creation involves analyzing source documents and architecture artifacts. This Skill automatically applies technical constraints, testing guidance, and implementation notes directly into the generated story markdown, ensuring all development guardrails are documented.

Yes, you can use BMAD artifacts to select the next backlog story for sprint planning. This Skill finds the next or specified story from your project artifacts and prepares it for development by pulling requirements from epics and updating sprint status.

Yes, story creation requires existing BMAD planning artifacts like PRDs, architecture notes, and epics. The Skill performs full analysis of these source documents to extract deep context, meaning it needs comprehensive upstream planning artifacts to generate a complete story.

Agile stories miss technical context when prior story learnings and architecture documents are not fully analyzed. This Skill solves that by extracting requirements from epics, UX notes, and previous learnings to produce exhaustive context with citations for the selected story.