bmad-dev-story

Automating story implementation involves parsing a story specification file and executing tasks using context from Dev Notes. This Skill follows a strict workflow including test-driven development, validation, and status updates to complete the process.

Automated test-driven development for agile stories works by adhering to a strict red-green-refactor cycle. The workflow parses story tasks, writes tests, implements code, runs validation steps, and updates the story status to review upon completion.

To implement development stories with context, you need to provide a detailed story specification file and access to project context or Dev Notes. Sprint status tracking may also be required for execution and updating task progress.

Yes, you can use workflow automation to update story status to review after coding. The Skill executes development tasks, writes tests, performs validation, and automatically updates the story file status to review upon finishing implementation.

The best way to execute tasks defined in a story specification file is by utilizing context-driven development. This approach strictly follows the provided requirements, applying a red-green-refactor cycle to ensure all implementation tasks are met accurately.

You should not use automated story implementation when a story specification file or project context is unavailable. Execution depends on parsing detailed story files and Dev Notes to adhere to the required test-driven development workflow.