bmad-dev-story

Story implementation follows a deterministic red-green-refactor sequence, writing failing tests first, adding minimal code to pass, then refactoring. It updates permitted story sections and transitions the status to review only after test and quality gates pass.

Red-green-refactor is a test-first workflow that writes failing tests, implements minimal code to pass them, then refactors while keeping tests green. It drives task completion by following the story's Tasks/Subtasks sequence exactly with strict modification boundaries.

Yes, story implementation resumes after a Senior Developer Review by prioritizing unresolved AI-Review follow-ups. It loads the specified story file, addresses the review items, runs regression checks, and updates the Dev Agent Record before marking the story for review.

Definition of done is tracked by satisfying regression checks and quality gates before marking a story for review. Documentation updates are limited to approved story sections only, including Tasks/Subtasks, File List, Change Log, and Status.

Yes, story implementation uses sprint-status.yaml ordering when available to locate the next ready-for-dev story. Alternatively, you can specify a direct story file path to load and implement end-to-end.

Modification boundaries restrict updates to approved story sections only: Tasks/Subtasks, Dev Agent Record, File List, Change Log, and Status. This strict scope prevents unintended changes and ensures the implementation satisfies the definition of done before transitioning to review.