bmad-validate-story

Automating story validation requires executing a predefined workflow in Validate mode to handle story preparation, verification, and progression. This process adopts a system-defined agent role to ensure consistency throughout the story cycle management workflow.

Story cycle management is the structured process of preparing, verifying, and progressing stories through validation. It works by initiating the cycle with a found story from the sprint plan and executing predefined workflows like VS, DS, and CR in sequence.

To start a story cycle from a sprint plan, you run an automated workflow that initiates the process using the first found story in the sprint plan. You can also trigger this cycle based on a specific epic and story context.

Yes, you can use system roles for workflow execution by adopting the role of an agent defined in the system's configuration file. This ensures consistency in workflows across agile development environments requiring structured validation.

Automated story progression relies on predefined workflows in Validate mode and a system configuration file for agent role adoption. It is limited to structured validation processes and may not handle ad-hoc story modifications outside the defined VS, DS, and CR workflow steps.