bmad-agent-dev

Test-first story implementation executes approved work through a disciplined red, green, refactor flow. It guides a developer persona through code changes while maintaining auditable tracking tied to acceptance criteria, tests, and file paths for verified delivery.

The BMad method workflow handles implementation-phase tasks including story completion, code review readiness, and sprint progression. It requires config loading, persona adoption, persistent fact loading, and menu-driven dispatch to execute software stories accurately.

Acceptance criteria completion is tracked by tying code changes directly to required tests and file paths. This keeps story implementation auditable, ensuring every criterion passes before the code delivery is verified and moved to code review readiness.

Yes, executing approved stories in a repository uses automated code verification to ensure every change meets acceptance criteria. It requires activation-step handling and config loading to maintain test-first discipline throughout the implementation workflow.

Removing guesswork from story implementation requires guiding a developer persona through approved work with test-first discipline. By maintaining clear acceptance-criterion tracking and verified delivery, progress stays auditable and tied to specific file paths and tests.

Yes, test-first story implementation requires activation-step handling, config loading, persona adoption, and persistent fact loading. These prerequisites ensure the menu-driven dispatch correctly executes implementation tasks within the BMad workflow environment.