bmad-dev-story

You can automate sprint story implementation by guiding agents through context-filled sprint story specifications, enforcing stepwise execution that covers loading context, red-green-refactor coding, and updating sprint status.

Enforce test-driven-development during story implementation by applying a stepwise execution flow that requires agents to follow red-green-refactor cycles, validate task completion with tests, and check Definition of Done criteria.

Maintain project context during dev-workflow execution by using context-driven loading of project and story information, which tailors implementation guidance and ensures architectural compliance for each sprint story.

Yes, you can update sprint-status and Definition of Done checks automatically because the workflow validates implemented tasks, updates sprint tracking, and generates documentation outputs as part of its stepwise execution flow.

You need to provide a sprint story file path to start the dev workflow, which the system uses to load project context, identify incomplete tasks, and guide the subsequent implementation steps.

Automated story implementation requires architectural guidance to ensure that the code generated by agents satisfies project-specific design constraints, passes Definition of Done checks, and maintains standardized auditable execution.