bmad-testarch-test-design

Automate risk-based test design planning for system and epic levels.

88|24|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-test-design-bmad-code-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-test-design
Source: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/workflows/testarch/bmad-testarch-test-design
Command: npx skills add https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-test-design-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The TEA Test Design unit provides a structured, repeatable approach to plan system- and epic-level QA activities around architecture decisions, risk assessment, NFR planning, and output generation.

Core Features & Use Cases

  • Workflow orchestration for two-mode design (system-level and epic-level)
  • Generation of architecture and QA design templates (test-design-architecture.md, test-design-qa.md, and epic-level outputs)
  • Integrated risk, NFR planning, coverage, and execution strategy artifacts
  • Handoff-ready outputs for BMAD integration

Quick Start

Start a new TEA design run by invoking the test-design workflow; it will auto-detect mode and produce the required design documents.

Frequently Asked Questions about bmad-testarch-test-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan risk-based testing for system-level architecture?

You can plan risk-based testing for system-level architecture by running a test-design workflow that automatically generates architecture documents, QA design templates, and risk assessment artifacts. It targets Phase 3 system-level planning to produce structured QA design outputs.

What is risk-based test design and when do I need NFR coverage artifacts?

Risk-based test design is a structured QA approach that aligns testing activities around architecture decisions and risk assessment. You need NFR coverage artifacts when planning system-level or epic-level testing to ensure non-functional requirements are validated.

How do I generate epic-level QA design documents and test coverage plans?

You generate epic-level QA design documents by invoking the test-design workflow, which auto-detects epic-level Phase 4 mode. It produces test-design-qa.md templates alongside integrated risk, coverage, and execution strategy artifacts.

Does BMAD TEA test design support handoff-ready outputs for QA workflows?

Yes, BMAD TEA test design produces handoff-ready outputs for QA workflows by generating architecture and QA design documents configured to BMAD artifacts. It enforces frontmatter-based context loading and knowledge fragments for seamless integration.

What's the best way to automate test design planning across system and epic scopes?

The best way to automate test design planning across system and epic scopes is to use a coordinated workflow that auto-detects the design mode. It targets Phase 3 and Phase 4 planning to automatically generate architecture, risk, NFR, and coverage artifacts.

Can I use architecture decisions to drive test execution strategy and coverage planning?

Yes, you can use architecture decisions to drive test execution strategy and coverage planning through the integrated risk assessment workflow. It generates QA design templates that align execution strategies with architecture decisions and NFR planning.