bmad-testarch-atdd

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

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-testarch-atdd-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-testarch-atdd
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-testarch-atdd-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams practicing TDD often skip the red phase or write acceptance tests after implementation, losing the design feedback loop. This Skill generates failing-first acceptance test scaffolds from a story's acceptance criteria before any code exists, complete with fixtures, data factories, and a developer handoff checklist. ## Core Features & Use Cases - Red-Phase Scaffold Generation: Creates E2E, API, and component tests marked with test.skip() following Given-When-Then structure, mapped to acceptance criteria with P0-P3 priorities. - Test Infrastructure: Generates 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 BMM story file for guest checkout, produce tests/e2e and tests/api scaffold files plus an ATDD checklist mapping each test to concrete implementation tasks for the dev team. ## Quick Start Ask the agent to write acceptance tests for a story file using ATDD, providing the path to the story markdown with its acceptance criteria.

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 tests emitted as test.skip() scaffolds, plus an implementation checklist developers activate one test at a time.

What test levels should I use for acceptance criteria?

The workflow applies a test-level selection framework: E2E for critical user journeys, API for business logic and service contracts, component for UI behavior, and unit for pure logic. It avoids duplicate coverage of the same behavior across levels.

Does this work with Cypress or only Playwright?

Both Playwright and Cypress configurations are detected during preflight. The optional playwright-utils mandate applies only to Playwright suites; Cypress projects follow the traditional fixture and network-first patterns instead.

Why do generated tests use test.skip() instead of failing directly?

Scaffolds ship skipped so the suite stays green until a developer activates the current task. The developer removes test.skip() for one test, confirms it fails for the right reason, then implements until it passes.

What happens if my story has no acceptance criteria?

The preflight step halts the workflow. Clear, testable acceptance criteria and an existing test framework configuration are hard prerequisites; the workflow will not generate scaffolds without them.