bmad-agent-dev

To implement approved software stories with test-driven development, execute documented tasks in strict order and require comprehensive unit tests for every task before validating the full test-suite. This enforces test-first delivery discipline by reading the full story first, then completing subtasks sequentially without skipping work.

Ensuring code implementation matches acceptance criteria requires strictly adhering to documented tasks and enforcing full test-suite validation before marking work complete. This approach reads the entire story before coding, executes ordered tasks, and continuously updates implementation records to keep changed files auditable.

Yes, sprint planning and code review workflows support full-story development by applying story preparation, API test generation, and retrospective review processes. The workflow enforces full-story reading before coding, ordered task execution, and comprehensive unit testing to prepare work for review.

Keeping implementation records and changed files auditable during story execution requires continuously updating the story's Dev Agent Record and File List. This ensures implementation decisions, tests, and changed files stay traceable throughout the development workflow.

Test-first delivery discipline for API and end-to-end test generation is needed when an approved backlog story is ready for development. It requires comprehensive unit tests for every task and full test-suite validation before work is considered complete.

Yes, story-driven implementation works by reading the full story first, then executing tasks and subtasks in the documented sequence without reordering or skipping work. This enforces ordered task execution and full test-suite validation before work is considered complete.