bmad-testarch-atdd

Orchestrates failing API and E2E acceptance tests for ATDD story criteria.

Updated Feb 11, 2026

Search Tags:#automation #planning #orchestration #red-green-refactor #fixtures #atdd #test-architecture

Ready to run

npx skills add https://github.com/mschuerig/peach-ios --skill bmad-testarch-atdd-mschuerig

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/mschuerig/peach-ios/tree/main/_bmad/tea/workflows/testarch/bmad-testarch-atdd
Command: npx skills add https://github.com/mschuerig/peach-ios --skill bmad-testarch-atdd-mschuerig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ATDD workflow helps teams generate and validate failing acceptance tests before implementing features, reducing ambiguity and guiding implementation.

Core Features & Use Cases

Orchestrates red-phase test generation for API and UI tests
Aggregates results and creates supporting ATDD artifacts (fixtures, checklist)
Provides deterministic workflows and guidance for testing teams

Quick Start

Trigger the ATDD workflow to generate intentionally failing API and E2E tests for a user story and capture the resulting artifacts.

Frequently Asked Questions about bmad-testarch-atdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate failing acceptance tests for ATDD workflows?▼

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.

What artifacts are produced when orchestrating ATDD red-phase test generation?▼

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.

How does ATDD test architecture map story acceptance criteria to test modes?▼

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.

Can I use this ATDD workflow to generate both API and E2E tests simultaneously?▼

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.

Why does acceptance test-driven development require intentionally failing tests first?▼

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.

What is the best way to coordinate red-green-refactor cycles for acceptance tests?▼

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.