bmad-testarch-test-design

Generate structured test-design artifacts from PRD/ADR inputs.

Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-testarch-test-design-cbanzaime23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-test-design
Source: https://github.com/Cbanzaime23/Booking-System/tree/main/.agent/skills/bmad-testarch-test-design
Command: npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-testarch-test-design-cbanzaime23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BMAD test design-architecture automation enables teams to convert product requirements into formal test-design artifacts, reducing ambiguity in planning and increasing governance.

Core Features & Use Cases

  • Generates risk assessments, coverage matrices, and execution strategies aligned with architecture decisions.
  • Produces BMAD-compliant system-level or epic-level plans and handoff documents for downstream workflows.
  • Supports both System-Level (Phase 3) and Epic-Level (Phase 4) planning with template-driven outputs and traceability.

Quick Start

Design a system-level or epic-level test plan by feeding the relevant PRD/ADR and let the skill generate the required artifacts.

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 generate a test plan from PRD and ADR inputs?

Test plan generation from PRD and ADR inputs automates structured test-design outputs by applying frontmatter-driven contracts and templates to produce formal coverage matrices, risk assessments, and execution strategies.

What is a system-level test design with risk focus?

System-level test design with risk focus is a structured planning approach that converts architecture decisions into formal test artifacts, enabling risk assessment, coverage matrices, and BMAD handoff generation for downstream workflows.

How do I create a BMAD-compliant handoff document for QA planning?

BMAD-compliant handoff documents for QA planning are created by applying template-driven outputs and traceability to PRD and ADR inputs, enforcing explicit field requirements like name, description, and a reusable workflow plan.

Does this test design skill support epic-level planning as well as system-level?

Yes, the test design skill supports both System-Level Phase 3 and Epic-Level Phase 4 planning, generating structured risk assessments and execution strategies aligned with architecture decisions for both scopes.

What are the required fields for generating a BMAD handoff document?

Required fields for generating a BMAD handoff document include a name, description, and a reusable workflow plan, enforced through a frontmatter-driven contract with optional references and supporting artifacts.

Why use a template-driven approach for architecture review test design?

A template-driven approach for architecture review test design reduces ambiguity in planning and increases governance by ensuring structured coverage matrices, explicit field requirements, and traceability across formal test artifacts.