bmad-create-story

Automating story creation in a sprint plan involves preparing the first found story for sequential execution. This Skill initiates the cycle by adopting a predefined agent role and executing a specific workflow to ensure the story is ready for next steps.

Sequential story preparation follows a defined workflow path of VS, DS, CR, and back to DS if needed. This ensures stories are systematically processed and validated before moving to the next development phase.

Yes, starting the story creation cycle requires a specific directory structure containing predefined agent roles and workflow files. The Skill reads and executes the workflow located in the provided _bmad/bmm/ directory path.

Yes, you can specify a specific epic and story with context during story creation. Alternatively, the workflow automatically prepares the first found story in the sprint plan if no specific story is targeted.

Agent role adoption for sprint planning works by assuming the role defined in a designated agent configuration file. This ensures the story creation process follows the exact responsibilities and constraints of that predefined role.

Automated sprint planning workflows are limited to predefined sequential steps and require a strict directory structure to function. They cannot dynamically alter the VS, DS, and CR execution path outside the established workflow parameters.