bmad-testarch-test-design

Generates risk-based system-level or epic-level test plans with coverage matrices and quality gates.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-test-design-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-test-design
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-testarch-test-design
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-test-design-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often start testing without a structured plan, leading to missed risks, duplicated coverage across test levels, and unclear quality gates. This Skill produces a disciplined, risk-grounded test design document before test implementation begins. ## Core Features & Use Cases - Dual-Mode Test Planning: Auto-detects system-level mode (PRD + ADR input, producing separate Architecture and QA documents plus a BMAD handoff) or epic-level mode (single epic test plan). - Risk Assessment Framework: Scores risks by probability and impact across TECH/SEC/PERF/DATA/BUS/OPS categories, with mitigation plans for high-priority risks (score >= 6). - Coverage and Execution Strategy: Maps requirements to P0-P3 priorities and test levels (E2E/API/Component/Unit), with interval-based effort estimates and PR/Nightly/Weekly execution tiers. - Use Case: After your architecture team finalizes an ADR for a new feature, run this workflow to produce a testability review for architects and a test execution recipe for QA, including NFR planning and quality gate criteria. ## Quick Start Ask the assistant to design a test plan for your epic or system using the PRD and architecture documents in the project.

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?

Provide the PRD and ADR or architecture docs, and the workflow runs in system-level mode. It produces two documents: an architecture-focused testability review with blockers and risks, and a QA execution recipe with coverage plans and effort estimates.

What is risk-based test design and how are risks scored?

Risk-based test design prioritizes testing by scoring each risk as probability (1-3) times impact (1-3). Risks scoring 6 or higher are high-priority and require documented mitigation plans with owners and timelines before testing proceeds.

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

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

Can I resume an interrupted test design workflow?

Yes. Each run writes a progress checkpoint named by run identity (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.

How are P0, P1, P2, and P3 test priorities assigned?

P0 covers critical business, security, or data-integrity behavior with no workaround; P1 covers core frequent behavior with limited workaround; P2 covers secondary behavior; P3 covers rare or cosmetic cases. Priority reflects importance, not execution timing.

When should I not use this test design workflow?

Skip it when prerequisites are missing: system-level mode requires a PRD and ADR, and epic-level mode requires stories with acceptance criteria. It also does not write actual test code; use the follow-on ATDD or automate workflows for that.