bmad-create-story

To generate a development story scaffold with acceptance criteria and dev notes, provide an epic-story identifier to automatically create a ready-to-edit file containing user stories, tasks, and project structure references.

Yes, story generation integrates with existing architecture and planning artifacts. It surfaces context from epics.md, prd.md, and architecture.md to preserve linkages to source documents during story creation.

Automating dev story creation during sprint planning is best handled by generating a complete story skeleton. This provides a deterministic output file path and templates so the dev agent can immediately proceed with implementation.

Yes, you can create a specific story by identifier. Providing an epic-story identifier like 1-2-user-auth triggers the automatic generation of a ready-to-use story file scaffold for that exact item.

Story generation includes guardrails and embedded context to ensure consistency and prevent interpretation errors. This encapsulates all context the dev agent needs to implement the story flawlessly.

You need to integrate with the BMAD workflow.md file to generate ready-to-use story context. This ensures the story skeleton aligns with established planning and architecture references.