bmad-story-planning

Breaking epics into developer-ready stories involves transforming high-level requirements into structured user stories with acceptance criteria, prerequisites, and task definitions. This skill automates that process by taking your PRD and architecture decisions as input and generating markdown story files with detailed breakdowns for sprint planning.

Acceptance criteria define the conditions a story must meet to be complete. This skill generates criteria by extracting requirements from your epic, linking them to architecture decisions, and structuring them as testable conditions developers can verify before marking a story done.

Yes. This skill produces structured markdown files for each story using predefined templates in its assets, plus a backlog summary that organizes all generated stories. You provide the epic and architecture context; it outputs ready-to-use story files and planning documents.

This skill injects traceable references to your PRD and architecture decisions directly into each generated story file. Dependencies and design rationale become part of the story artifact, so developers understand the context behind each task without hunting for external documents.

Provide your input as JSON or structured data containing the epic description and relevant architecture decisions. The skill processes this data through its story generation templates to produce developer-ready output files organized in a stories/ directory.

Yes. This skill applies when a PRD and architecture decisions already exist and epics are defined. It requires these inputs to generate accurate stories and link them to design context; it does not create strategy or high-level planning from scratch.