bmad-testarch-atdd

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-atdd-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-testarch-atdd
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-atdd-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

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-ready implementation checklist. ## Core Features & Use Cases - Red-Phase Scaffold Generation: Creates E2E, API, and component tests marked with test.skip() that fail for the right reasons once activated, following Given-When-Then structure. - Test Infrastructure: Produces faker-based data factories, auto-cleanup Playwright fixtures, 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 checklist-based validation. - Use Case: Given a user story for guest checkout with five acceptance criteria, the Skill maps each criterion to prioritized E2E and API tests, generates the scaffolds, and hands developers a task-by-task red-green-refactor roadmap. ## 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 test levels, generates scaffolds marked with test.skip(), and produces an implementation checklist developers activate one test at a time.

What test levels does ATDD test generation support?

The workflow supports E2E tests for critical user journeys, API tests for business logic and contracts, component tests for UI behavior, and unit tests for pure logic. Level selection adapts to the detected stack: frontend, backend, fullstack, or mobile.

Does the ATDD workflow work with Cypress or only Playwright?

Both Playwright and Cypress configurations are detected during preflight. Playwright projects can optionally enforce the playwright-utils mandate, while Cypress suites follow traditional fixture and network-first patterns instead.

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

Scaffolds use test.skip() so the suite stays green until a developer activates the current task. Removing the skip for one test confirms it fails for missing implementation, not test bugs, which is the verified TDD red phase.

What happens if my story has no acceptance criteria?

The preflight step halts the workflow. Testable acceptance criteria and an existing test framework configuration are hard prerequisites, since scaffolds cannot be derived without them.

Can I resume an interrupted ATDD workflow run?

Yes. The output checklist tracks progress in YAML frontmatter with stepsCompleted and lastStep fields. Selecting Resume mode loads that file, displays a progress dashboard, and routes to the next incomplete step.