bmad-testarch-atdd

To generate failing acceptance tests for ATDD, you map story acceptance criteria to test disciplines and modes. This orchestrates worker subagents to produce intentionally failing API and E2E tests, validating red-phase constraints before implementation begins.

Orchestrating ATDD red-phase test generation produces a structured artifact set including test files, fixtures, and an ATDD checklist with red-green-refactor guidance. These outputs coordinate API and E2E results aggregation to guide subsequent implementation.

ATDD test architecture maps story acceptance criteria to specific test disciplines and modes by coordinating generation worker subagents. It validates red-phase constraints and aggregates API and E2E test outputs into structured artifacts.

Yes, this ATDD workflow coordinates API and E2E generation worker subagents simultaneously. It aggregates results from both test disciplines while validating red-phase constraints, producing unified test files and fixtures for a user story.

Acceptance test-driven development requires intentionally failing tests first to reduce ambiguity and guide implementation. Validating red-phase constraints ensures tests accurately reflect story acceptance criteria before any feature code is written.

The best way to coordinate red-green-refactor cycles is by triggering an ATDD workflow that generates an accompanying checklist. This checklist provides deterministic guidance alongside failing test files and fixtures to structure your implementation phase.