bmad-dev-story

To execute story implementation, load a context-filled spec file into the sprint workflow to trigger automated red-green-refactor cycles, test creation, and DoD validation directly from your story files.

A red-green-refactor cycle in test-driven development is an iterative process where you write a failing test, write code to pass the test, and then refactor the code while maintaining test validation across story files.

Yes, you can resume a paused story implementation by loading its context spec file, executing the first incomplete task, and iteratively validating progress with tests until all DoD criteria are satisfied.

Yes, the story workflow provides structured architecture guidance, risk assessment, and implementation traceability across tasks and subtasks to ensure alignment with project specifications.

The best way to track sprint status and Dev Notes is to automate updates directly from your story files, ensuring file tracking, task completion, and DoD validation are recorded as artifacts throughout the development cycle.

Yes, you need context-filled spec files as input to run the dev story workflow, because the automated execution, test generation, and sprint-status updates depend entirely on the context provided within those story files.