diff --git a/src/bmm-skills/4-implementation/bmad-dev-story/workflow.md b/src/bmm-skills/4-implementation/bmad-dev-story/workflow.md
index 4164479c3..f68aea667 100644
--- a/src/bmm-skills/4-implementation/bmad-dev-story/workflow.md
+++ b/src/bmm-skills/4-implementation/bmad-dev-story/workflow.md
@@ -157,6 +157,31 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+
+ Search {test_artifacts} for an ATDD checklist matching pattern: `atdd-checklist-{{story_key}}*.md` or `*{{story_key}}*atdd*.md`
+
+
+ Continue without ATDD checklist? [y] proceed anyway · [n] halt and run testarch-atdd first:
+
+ HALT — run /bmad-testarch-atdd for {{story_key}} before continuing
+
+
+
+ Scan checklist for Gherkin scenarios (lines starting with Given/When/Then or Feature:/Scenario:)
+
+
+
+
+
+
Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status
Load comprehensive context from story file's Dev Notes section
@@ -267,7 +292,8 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
Plan implementation following red-green-refactor cycle
- Write FAILING tests first for the task/subtask functionality
+ Identify test type for this task: unit test (business logic / API) or E2E test (user-facing screen / navigation flow)
+ Write FAILING test of the appropriate type first — unit test for logic, E2E test for UI flows
Confirm tests fail before implementation - this validates test correctness
@@ -294,7 +320,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
Create unit tests for business logic and core functionality introduced/changed by the task
Add integration tests for component interactions specified in story requirements
- Include end-to-end tests for critical user flows when story requirements demand them
+ Include end-to-end tests for all user-facing flows; unit tests are mandatory for all business logic and API routes
Cover edge cases and error handling scenarios identified in story Dev Notes
@@ -372,7 +398,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
- Implementation satisfies every Acceptance Criterion
- Unit tests for core functionality added/updated
- Integration tests for component interactions added when required
- - End-to-end tests for critical flows added when story demands them
+ - End-to-end tests added for all user-facing flows (unit tests for logic/API routes)
- All tests pass (no regressions, new tests successful)
- Code quality checks pass (linting, static analysis if configured)
- File List includes every new/modified/deleted file (relative paths)