bmad-create-story

To automate dev-story generation, you provide epic and story identifiers to synthesize a structured Markdown file. This file embeds context, guardrails, and implementation guidance, creating a ready-for-dev document with status and references.

A ready-for-dev story file is a formalized Markdown document that guides developers through implementation. It includes structured templates, previous story intelligence, architecture constraints, acceptance criteria, status, and source hints for traceability.

Yes, you can use existing story templates by providing a story template path. The system applies the structured format, embedding guardrails and previous story intelligence to produce a consistent, ready-for-dev Markdown file.

Yes, dev-story generation explicitly applies to epic and story workflows. It streamlines story file creation by aligning with sprint planning templates, ensuring consistency and traceability across stories within the epic.

You enforce architecture constraints and guardrails by using a story generation process that automatically embeds them into the structured template. This ensures the output Markdown file contains the necessary implementation guidance and acceptance criteria.

The best way to create consistent story files is to use an automated story synthesis tool. It applies a structured template, includes previous story intelligence, and outputs a ready-for-dev Markdown file with status and dependencies for immediate implementation.