bmad-agent-dev

To execute software stories with test-driven development, you need a developer agent that reads the story file first, follows tasks in order, and creates comprehensive tests before marking work complete. This ensures strict traceability and adherence to acceptance criteria.

Test-driven story execution is a disciplined workflow where a developer agent reads an approved story file, implements code changes in specified order, creates and runs comprehensive tests, and validates the full test suite passes before delivery.

To ensure code changes meet acceptance criteria for review-ready delivery, use a developer workflow that executes ordered tasks from the story file, runs full test-suite validation, and updates documentation for changed files and implementation records.

Yes, you can automate test creation and full test-suite validation by using a senior engineer persona agent that implements planned changes, generates comprehensive tests, and validates the entire suite passes before marking the story complete.

Test-driven story execution works without external dependencies, relying solely on the approved story file as input. The agent reads the story, implements changes, creates tests, and updates records independently within your software engineering project.

The limitation of this developer agent approach is that it requires pre-approved story files with clearly defined tasks and acceptance criteria. It executes stories in order and cannot handle unplanned changes or stories lacking structured task specifications.