bmad-dev-story

Story implementation from contextual specs is executed by loading architecture guidance and acceptance criteria, then enforcing a red-green-refactor cycle to produce verifiable code changes. This ensures test-first discipline and quality throughout the workflow.

A red-green-refactor cycle in story implementation is a test-driven development process where failing tests are written first, code is written to pass them, and then the code is refactored. This Skill enforces this cycle alongside documentation updates.

Sprint management and story implementation are automated by updating sprint-status tracking and maintaining a traceable change log and Dev Agent Record. This integrates task tracking directly into the implementation workflow for audit-ready results.

Yes, story implementation validates changes against acceptance criteria and Definition of Done (DoD). The workflow loads this context from the story spec to drive implementation and ensures artifact creation aligns with these validation requirements.

Automated code review during story implementation is supported through structured workflow execution and DoD validation. By enforcing test creation and maintaining a Dev Agent Record, it produces verifiable, audit-ready changes aligned with acceptance criteria.

To start a story implementation, you need to provide the story file path and initiate the workflow. The system then loads the complete context-rich story spec, including architecture guidance and acceptance criteria, to drive the implementation process.