bmad-create-story

To generate a dev story, you provide the epic or story identifier along with workflow inputs. The tool analyzes planning artifacts, architecture constraints, and previous stories to output a production-grade story file with tasks, tests, and guardrails.

A ready-for-dev story file includes the story statement, acceptance criteria, actionable tasks, developer notes, testing guidelines, deployment considerations, and references to project context and architecture.

Consolidating PRDs and UX guidelines happens automatically by integrating inputs from epics, architecture, and UX to ensure alignment. It enforces strict structure and references to produce a unified implementation document.

Yes, you can hand the generated story directly to a dev-agent. It provides operational guidance, project structure recommendations, and strict structural enforcement to ensure the agent receives complete context.

Generating story files does not strictly require previous stories, but it analyzes them if available. Analyzing previous stories helps maintain strict structure, references, and project context alignment across the workflow.

Automated story generation streamlines the consolidation of epic requirements, architecture constraints, and workflow guidelines into a single document. This prevents context loss and provides embedded operational guidance for development teams.