bmad-create-story

To generate a ready-for-dev story file, provide the epic number and story number. The process analyzes your planning artifacts, project context, and templates to consolidate all required context into a single document for the dev-agent.

A ready-for-dev story file is a consolidated document containing all cross-cut context, guardrails, and planning references a dev-agent needs to implement a specific story, ensuring consistency with project standards and eliminating manual assembly.

You can create aligned story files by providing the epic and story identifiers. The generation process automatically analyzes your existing epics, prd, and architecture planning artifacts to ensure the output adheres to your template structure.

Yes, the generated story file integrates directly with the sprint status and workflow described in your workflow.md. It produces a document designed to be loaded by the dev-agent and validated against the project checklist.

You need to provide the epic number and story number, or the full story key. The process then uses these inputs alongside your project's planning artifacts, templates, and context engine to generate the complete story file.

Yes, the generated story file includes guardrails by aligning with your planning artifacts and architecture. This ensures the dev-agent receives cross-cut context and project standards directly within the ready-for-dev document.