Atdd
npx machina-cli add skill PabloLION/bmad-plugin/atdd --openclawTestarch Atdd Workflow
Goal: Generate failing acceptance tests using TDD cycle.
Agent: Master Test Architect and Quality Advisor (Murat) Module: TEA
Execution
Select a sub-workflow based on user intent:
| Trigger | Sub-workflow | Description |
|---|---|---|
| PL | ./workflow-plan.md | plan |
Read and follow the selected sub-workflow file.
Validation
After completion, verify against: ./checklist.md
Source
git clone https://github.com/PabloLION/bmad-plugin/blob/main/plugins/bmad/skills/atdd/SKILL.mdView on GitHub Overview
Testarch ATDD Workflow generates failing acceptance tests using a TDD cycle. It guides you to select a sub-workflow, follow a plan file, and verify results against a checklist. This approach keeps acceptance criteria aligned with user needs.
How This Skill Works
The agent, Master Test Architect and Quality Advisor Murat, orchestrates the TEA module to run ATDD on user intent. You trigger the flow with phrases that indicate ATDD, which selects a sub-workflow such as PL for planning. The system reads the chosen sub-workflow file, executes steps, and ends with a validation against the checklist file.
When to Use It
- The user explicitly asks to write acceptance tests, e.g., lets write acceptance tests or I want to do ATDD.
- You need to start ATDD to drive the creation of failing tests before implementation.
- A planning step is required and you want to trigger the PL sub-workflow via workflow-plan.md.
- You want to read and follow a referenced sub-workflow file before implementation.
- Post-execution you must verify results against the checklist in ./checklist.md.
Quick Start
- Step 1: Trigger ATDD by saying lets write acceptance tests or I want to do ATDD.
- Step 2: Use the PL trigger to generate the workflow-plan.md and read it.
- Step 3: Follow the selected sub-workflow, then run validation against ./checklist.md.
Best Practices
- Define clear acceptance criteria before writing tests to drive intentional failures.
- Follow the TDD cycle: fail first, then implement to pass, then refactor.
- Use the PL sub-workflow via ./workflow-plan.md to generate a concrete plan.
- Read and apply the selected sub-workflow file to ensure reproducible steps.
- Validate all results against the documented checklist at ./checklist.md.
Example Use Cases
- Plan and generate a failing login acceptance test using the ATDD workflow.
- ATDD for a shopping cart checkout to ensure all acceptance criteria are captured.
- ATDD for user registration with required fields and error messaging.
- Plan a data export feature and validate with a checklist-based acceptance test.
- Align acceptance criteria with a requirements document using ATDD to drive test failures first.