bmad-testarch-atdd

Generate red-phase acceptance test scaffolds from story acceptance criteria using the TDD cycle.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-atdd-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-testarch-atdd
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-atdd-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams practicing acceptance test-driven development often write tests after implementation, losing the design feedback that failing-first tests provide. This Skill generates red-phase acceptance test scaffolds before any code exists, mapping story acceptance criteria to E2E, API, and component tests with fixtures, factories, and an implementation checklist for developers. ## Core Features & Use Cases - Red-Phase Scaffold Generation: Creates Playwright or Cypress test files marked with test.skip() across E2E, API, and component levels, each mapped to acceptance criteria and P0-P3 priorities. - Test Infrastructure: Generates faker-based data factories, auto-cleanup fixtures, mock requirements, and required data-testid attribute lists for the DEV team. - 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 with five acceptance criteria, produce skipped E2E and API test scaffolds, factories, fixtures, and an ATDD checklist that developers activate one test at a time through red-green-refactor. ## 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 test 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 test generation support?

The workflow selects between E2E, API, component, and unit levels based on stack detection (frontend, backend, fullstack, or mobile). E2E covers critical user journeys, API covers business logic and contracts, and component tests cover UI behavior.

Does this work with Playwright and Cypress test frameworks?

Yes, it detects playwright.config.ts or cypress.config.ts during preflight and adapts generation accordingly. When the playwright-utils flag is enabled, scaffolds use interceptNetworkCall, apiRequest, and recurse instead of vanilla Playwright calls.

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

Scaffolds are intentionally skipped because they represent the TDD red phase before implementation exists. Developers remove test.skip() for one test at a time, confirm it fails, then implement the minimal code to make it pass.

Can I resume an interrupted ATDD workflow run?

Yes, the workflow saves progress in YAML frontmatter after each step. Selecting Resume mode loads the output document, displays completed steps, and routes to the next incomplete step without re-executing finished work.