bmad-testarch-atdd

Generates red-phase acceptance test scaffolds with fixtures, factories, and implementation checklists.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-testarch-atdd-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-testarch-atdd
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-testarch-atdd-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams practicing TDD often skip writing acceptance tests before implementation, losing the red-green-refactor discipline. This Skill generates failing (red-phase) acceptance test scaffolds from a story's acceptance criteria before any code exists, complete with fixtures, data factories, and a developer implementation checklist. ## Core Features & Use Cases - Red-Phase Test Generation: Creates E2E, API, and component test scaffolds marked with test.skip() that fail only when activated, mapped to acceptance criteria with P0-P3 priorities. - Test Infrastructure: Produces faker-based data factories, Playwright fixtures with auto-cleanup, mock requirements, and required data-testid attribute lists. - Tri-Modal Workflow: Supports Create, Resume, Validate, and Edit modes with step-file architecture, progress tracking frontmatter, and a validation checklist. - Use Case: Given a user story for guest checkout, generate Playwright E2E and API scaffolds plus an ATDD checklist that the dev team activates one test at a time during implementation. ## Quick Start Ask the agent to write acceptance tests for a story file, for example: run ATDD for docs/stories/2-4-guest-checkout.md and generate the red-phase scaffolds.

Frequently Asked Questions about bmad-testarch-atdd

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

FAQPage Schema
How do I write acceptance tests before implementation with ATDD?

Provide a story file with clear acceptance criteria and run the ATDD workflow. It maps each criterion to E2E, API, or component test levels, then generates test.skip() scaffolds that developers activate one at a time during the red-green-refactor cycle.

What test levels does ATDD generate for a user story?

The workflow selects levels based on stack detection: E2E for critical user journeys, API for business logic and contracts, and component tests for UI behavior. Backend-only projects use unit, integration, and API levels without browser tests.

Does the ATDD workflow support Playwright and Cypress?

Yes, it detects the framework from playwright.config.ts or cypress.config.ts and generates matching scaffolds. When the playwright-utils flag is enabled, generated specs must use interceptNetworkCall, apiRequest, and merged fixtures instead of vanilla Playwright calls.

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

Scaffolds are red-phase by design: they must not run as passing tests before implementation exists. Developers remove test.skip() for one test at a time, confirm it fails for the right reason, then implement the minimal code to make it pass.

What happens if the story has no acceptance criteria?

The workflow halts at the preflight step. Clear, testable acceptance criteria and an existing test framework configuration are hard prerequisites, so the run stops and notifies the user rather than generating ungrounded tests.