bmad-testarch-atdd

Generate red-phase acceptance test scaffolds using the TDD red-green-refactor cycle.

Updated May 7, 2026
One-click install
npx skills add https://github.com/jgabriellima/deep-agent-skill --skill bmad-testarch-atdd-jgabriellima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/bmad-testarch-atdd
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill bmad-testarch-atdd-jgabriellima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams practicing acceptance test-driven development need failing test scaffolds written before implementation begins, but manually mapping acceptance criteria to E2E, API, and component tests is slow and inconsistent. ## Core Features & Use Cases - Red-Phase Test Generation: Creates E2E, API, and component test scaffolds marked with test.skip() that fail until implementation exists. - Test Strategy Mapping: Converts story acceptance criteria into prioritized (P0-P3) scenarios at the appropriate test level based on detected stack (frontend, backend, fullstack). - Supporting Infrastructure: Produces data factories with faker, fixtures with auto-cleanup, mock requirements, and data-testid lists for the dev team. - Use Case: Given an approved user story for a registration feature, generate Playwright API and E2E scaffolds plus an ATDD checklist that hands the dev team a red-green-refactor implementation roadmap. ## Quick Start Ask the agent to run the ATDD workflow for your approved story file to generate red-phase acceptance test scaffolds and an implementation checklist.

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 acceptance tests before implementation with ATDD?▼

Run the workflow with an approved story file containing testable acceptance criteria. It maps each criterion to E2E, API, or component test levels and emits Playwright test files marked with test.skip() so they fail only when activated by the developer.

What test levels does ATDD test generation support?▼

The workflow selects levels based on detected stack: E2E, API, and component tests for frontend or fullstack projects, and unit, integration, and API/contract tests for backend projects. It avoids duplicate coverage across levels.

Does this workflow support Playwright and Cypress?▼

Yes, it detects the framework from playwright.config.ts or cypress.config.ts during preflight. For backend stacks it looks for configs like conftest.py or Go test files, and halts if no framework scaffolding exists.

Can I use Pact contract testing with ATDD scaffolds?▼

Yes, when the tea_use_pactjs_utils config flag is enabled, the API subagent also generates Pact consumer contract tests with provider scrutiny evidence. It enforces one pact.addInteraction() per test block for PactV4 compatibility.

Why are generated tests marked with test.skip()?▼

Tests are red-phase scaffolds in the TDD cycle: they assert expected behavior but stay skipped until a developer activates one for the current task. This prevents CI failures while documenting intentional pre-implementation tests.

What happens if my story has no acceptance criteria?▼

The workflow halts during the preflight step. Clear, testable acceptance criteria and an existing test framework configuration are hard prerequisites that must be resolved before any scaffolds are generated.