bmad-testarch-test-design

Generate risk-based test plans and coverage matrices from PRD, ADR, and epic documents.

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-testarch-test-design-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-test-design
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-testarch-test-design
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-testarch-test-design-pastasus

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 so QA and engineering know exactly what to test, at which level, and in what priority order. ## Core Features & Use Cases - Dual-Mode Test Planning: Auto-detects system-level mode (PRD + ADR, producing separate Architecture and QA documents plus a BMAD handoff) or epic-level mode (single epic test plan). - Risk Assessment & Scoring: Classifies risks by category (TECH/SEC/PERF/DATA/BUS/OPS), scores probability × impact, and defines mitigation plans with owners and timelines for high-priority risks. - Coverage & Execution Strategy: Maps requirements to P0-P3 priorities and test levels (E2E/API/Component/Unit), with interval-based effort estimates and a simple PR/nightly/weekly execution strategy. - Use Case: After your architecture review, ask the agent to design a test plan from your PRD and ADR; it produces a testability concerns document for architects, a test execution recipe for QA, and a handoff document for epic/story decomposition. ## Quick Start Ask the agent to design a test plan from your PRD and architecture documents, or name a specific epic to plan its test coverage.

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 your PRD and ADR or architecture docs, and the workflow runs in system-level mode. It produces two documents: an architecture-focused testability concerns report and a QA execution recipe with prioritized coverage.

How does risk-based test prioritization work with P0 to P3 levels?

Risks are scored as probability (1-3) times impact (1-3), with scores of 6 or higher flagged as high priority. Scenarios are then classified P0 through P3 by business impact and workaround availability, with risk scores as supporting evidence.

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 to produce 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.

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 documentation with clear, testable acceptance criteria.