bmad-testarch-atdd

Generate failing acceptance tests from story criteria with ATDD handoff checklists.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-testarch-atdd-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-testarch-atdd
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-testarch-atdd-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns acceptance criteria into a structured ATDD plan so teams can create failing tests before implementation, reducing ambiguity and speeding up test-first delivery.

Core Features & Use Cases

  • Preflight validation: Checks story readiness, framework availability, and project context before generating tests.
  • Test strategy mapping: Translates acceptance criteria into prioritized test levels such as E2E, API, component, and unit coverage where appropriate.
  • Red-phase generation: Produces intentionally failing tests with supporting fixtures, mock requirements, and implementation checklists.
  • Workflow orchestration: Handles create, resume, validate, and edit modes for an end-to-end ATDD process.
  • Use case: A QA or engineering lead can feed in a story and get a complete set of failing tests plus a handoff checklist for the development team.

Quick Start

Ask the ATDD skill to analyze a user story and generate failing acceptance tests with a checklist for implementation handoff.

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 failing acceptance tests from story criteria for TDD red-phase?

You can generate failing acceptance tests by feeding a user story into the ATDD workflow, which maps acceptance criteria to prioritized test levels and produces red-phase tests with fixtures and mock requirements. The output includes an implementation checklist for development handoff.

What is ATDD test strategy mapping and how does it translate acceptance criteria?

ATDD test strategy mapping translates story acceptance criteria into prioritized test coverage levels, including E2E, API, component, and unit tests. It structures the red-phase planning process to ensure failing tests are created before implementation begins.

How do I validate story readiness before generating acceptance tests?

Preflight validation checks story readiness, framework availability, and project context before generating acceptance tests. This ensures the user story and test framework are properly configured to support a structured ATDD plan and red-phase generation.

Can I use Playwright for acceptance test-driven development workflows?

Playwright is supported within the ATDD workflow for generating failing acceptance tests. The skill maps acceptance criteria to appropriate test levels, including E2E coverage, and produces red-phase tests with supporting fixtures for implementation handoff.

What is the best way to orchestrate an acceptance test-driven development process?

Workflow orchestration handles create, resume, validate, and edit modes for an end-to-end ATDD process. This allows teams to manage the full lifecycle of failing test generation, from preflight checks through red-phase test creation to implementation handoff.

Do I need a complete user story to generate failing acceptance tests?

A complete user story with defined acceptance criteria is required. The skill performs preflight validation to check story readiness before generating the ATDD plan, ensuring sufficient context exists to produce meaningful failing tests and mock requirements.