bmad-testarch-test-design

Generates risk-based test plans with coverage matrices and execution strategies for epics or systems.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-testarch-test-design-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-test-design
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-testarch-test-design
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-testarch-test-design-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often start testing without a structured plan, leading to duplicated coverage, missed high-risk areas, and unclear quality gates. This Skill produces a disciplined, risk-grounded test design document before any test code is written. ## Core Features & Use Cases - Dual-Mode Test Planning: Runs in system-level mode (PRD + ADR input, producing separate Architecture and QA documents plus a BMAD handoff) or epic-level mode (single test plan per epic). - Risk Assessment & Prioritization: Scores risks by probability and impact across TECH/SEC/PERF/DATA/BUS/OPS categories and maps them to P0-P3 test scenarios with no duplicate coverage across test levels. - Tri-Modal Workflow: Supports Create, Resume (with per-run progress checkpoints), Validate (against a built-in checklist), and Edit modes. - Use Case: After finishing a PRD and architecture decision record, run this Skill to produce a test-design-architecture.md for the engineering team and a test-design-qa.md execution recipe for QA, including effort estimates and quality gate criteria. ## Quick Start Ask the assistant to design a test plan for your epic or system using the bmad-testarch-test-design workflow and provide your PRD, ADR, or epic story 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 create a test plan from a PRD and architecture document?

Run this workflow in system-level mode with your PRD and ADR as inputs. It generates two documents: an architecture-focused file with testability concerns and blockers, and a QA-focused file with the coverage plan, execution strategy, and effort estimates.

How does risk-based test prioritization work in this workflow?

Each risk is scored by probability (1-3) times impact (1-3) and categorized as TECH, SEC, PERF, DATA, BUS, or OPS. Risks scoring 6 or higher require mitigation plans, and scenarios are assigned P0-P3 priorities based on business impact and workaround availability.

What is the difference between system-level and epic-level test design?

System-level mode uses PRD plus ADR inputs and produces separate Architecture and QA documents plus a BMAD handoff. Epic-level mode uses epic stories with acceptance criteria and produces a single test plan document per epic.

Can I resume an interrupted test design workflow?

Yes. Each run writes a progress checkpoint named by its run key (system or epic number). Resume mode loads the matching checkpoint, shows completed steps, and routes to the next incomplete step without re-executing finished work.

What inputs are required before running a test design workflow?

System-level mode requires a PRD with functional and non-functional requirements plus an ADR or architecture document. Epic-level mode requires epic or story markdown with clear acceptance criteria. Missing prerequisites cause the workflow to halt and request them.

When should I not use this test design workflow?

Skip it when you need actual test code rather than a plan. This workflow produces planning documents only; generating P0 acceptance tests requires the separate ATDD workflow, and full test automation uses the automate workflow.