bmad-testarch-test-design

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

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

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 before any test code is written. ## Core Features & Use Cases - Dual-Mode Test Planning: Generates either a system-level design (architecture concerns doc plus QA execution recipe plus BMAD handoff) or a single epic-level test plan, auto-detected from PRD/ADR versus epic/story inputs. - 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. - Resumable Step-File Workflow: Runs create, resume, validate, and edit modes with per-run progress checkpoints, a validation checklist, and NFR planning that defers final verdicts to a later assessment. - Use Case: Given a PRD and ADR for a new feature, produce a test-design-architecture.md listing pre-implementation blockers and a test-design-qa.md with a prioritized coverage plan, execution strategy, and interval-based effort estimates. ## Quick Start Ask the assistant to design a test plan for your PRD and architecture documents, or for a specific epic with its stories.

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 an architecture-facing document with blockers and risk mitigations plus a QA-facing document with the coverage plan, execution strategy, and effort estimates.

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 and story acceptance criteria and generates a single test plan document for that epic.

How are test priorities P0 through P3 assigned?

Priorities reflect business impact, user reach, and workaround availability, with risk scores as supporting evidence rather than a strict requirement. P0 covers critical functionality with no workaround, while P3 covers rare or cosmetic behavior.

Can I resume an interrupted test design workflow?

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

Does the workflow decide whether NFRs pass or fail?

No. It only plans NFR validation by mapping categories like security and performance to thresholds, tools, and evidence artifacts. Final PASS, CONCERNS, or FAIL decisions are deferred to the separate nfr-assess workflow after implementation evidence exists.