bmad-testarch-atdd

Generate red-phase ATDD scaffolds for frontend and backend test architectures.

88|24|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-atdd-bmad-code-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/workflows/testarch/bmad-testarch-atdd
Command: npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-atdd-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the generation and validation of red-phase ATDD scaffolds for software test architectures within the TEA workflow, enabling consistent, knowledge-driven outputs.

Core Features & Use Cases

  • Centralizes ATDD workflow steps for test-architecture planning across frontend and backend projects.
  • Generates red-phase API and E2E scaffolds, ATDD checklists, and supporting data (factories, fixtures) with deterministic frontmatter.
  • Validates outputs against workflow plans and knowledge fragments, then aggregates results for handoff to the DEV team.

Quick Start

Load the TEA ATDD story context and activate the bmad-testarch-atdd workflow to begin red-phase scaffolding.

Frequently Asked Questions about bmad-testarch-atdd

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

FAQPage Schema
What is red-phase ATDD scaffolding for test architecture?

Red-phase ATDD scaffolding generates failing test structures for API, E2E, and component layers before implementation. It enforces test-first discipline by producing ATDD checklists and supporting data artifacts like factories and fixtures with standardized frontmatter.

How do I generate ATDD test scaffolds for both frontend and backend projects?

You can generate ATDD test scaffolds by loading the TEA ATDD story context and activating the orchestration workflow. It automates red-phase scaffold generation, validates outputs against workflow plans, and aggregates results for developer handoff.

Does this ATDD workflow support Playwright and Pact for E2E and contract testing?

Yes, the ATDD workflow integrates with Playwright for E2E testing and Pact for contract testing. It applies red-phase discipline across frontend and backend architectures, producing deterministic scaffolds and data artifacts for these frameworks.

Can I use this to create ATDD checklists and test data factories for my project?

Yes, the workflow generates ATDD checklists alongside supporting data artifacts including factories and fixtures. It centralizes test-architecture planning and applies standardized frontmatter to ensure deterministic, knowledge-driven outputs for team handoff.

What's the best way to enforce red-phase discipline in test architecture planning?

The best way to enforce red-phase discipline is through automated orchestration that validates scaffolds against knowledge fragments and workflow plans. This ensures consistent test-first outputs before passing aggregated results to the development team.

Why do I need standardized frontmatter in ATDD test scaffolds?

Standardized frontmatter guides activation and handoff within the TEA framework. It ensures generated API, E2E, and component scaffolds remain deterministic and knowledge-driven, enabling consistent validation against workflow plans across teams.