bmad-testarch-atdd

Generate red-phase API and E2E test scaffolds from acceptance criteria.

1|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-testarch-atdd-mazenmrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-atdd
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-testarch-atdd
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-testarch-atdd-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

BMAD ATDD automates the generation and validation of red-phase scaffolds used in acceptance test-driven development, enabling deterministic workflow orchestration and auditable artifacts before implementation.

Core Features & Use Cases

  • Generates red-phase API and E2E test scaffolds from story acceptance criteria.
  • Orchestrates multi-step ATDD workflow including aggregation, validation, and knowledge-base references.
  • Produces a downloadable ATDD checklist, fixture scaffolds, and integration artifacts for story handoff.
  • Supports worker subagents for API and E2E scaffold generation with red-phase scaffolds.
  • Integrates with knowledge fragments to guide scaffold design and quality criteria.

Quick Start

Use the BMAD ATDD workflow to generate red-phase test scaffolds for a user story by selecting the Create path and reviewing the ATDD checklist and 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 generate red-phase ATDD test scaffolds from acceptance criteria?

You can generate red-phase ATDD test scaffolds by inputting story acceptance criteria and workflow context, which the tool uses to automatically produce API and E2E test scaffolds marked with test.skip(). It outputs an ATDD checklist, fixtures, and artifacts for story handoff.

What is automated red-phase scaffolding in acceptance test-driven development?

Automated red-phase scaffolding creates skipped test structures for API and E2E layers before implementation begins. It enforces test.skip() on generated scaffolds, ensuring deterministic workflow orchestration and auditable artifacts prior to writing application code.

Can I validate and edit existing ATDD scaffolds instead of creating new ones?

Yes, the tool supports create, validate, and edit modes for ATDD scaffolds. You can validate existing test artifacts against acceptance criteria or edit generated scaffolds using multi-agent orchestration to ensure quality criteria are met.

How do ATDD scaffolds integrate with downstream development workflows?

Generated ATDD scaffolds link directly into story metadata for downstream workflows. The tool writes artifacts to configured paths and produces integration artifacts, ensuring seamless handoff between test generation and implementation phases.

Does the tool support multi-agent orchestration for test scaffold generation?

Yes, it orchestrates worker subagents for both API and E2E scaffold generation within the ATDD workflow. This multi-agent approach handles aggregation, validation, and knowledge-base references to guide scaffold design.

What limitations exist when using test.skip() for red-phase scaffolding?

Red-phase scaffolds use test.skip() to prevent execution until implementation is complete, meaning tests remain inactive initially. This approach focuses on structure and auditable artifacts rather than runtime validation during the scaffold generation phase.