bmad-testarch-test-design

Create system-level or epic-level test plans grounded in risk assessment and coverage prioritization.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-test-design-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-test-design
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-testarch-test-design
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-test-design-hordricjr

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 risk-based test design document that maps requirements to prioritized test scenarios before implementation begins. ## Core Features & Use Cases - Dual-Mode Test Planning: Generates either a system-level design (architecture concerns doc plus QA execution doc) or an epic-level test plan, auto-detected from available PRD, ADR, and story artifacts. - Risk Assessment Matrix: Classifies risks by category (TECH/SEC/PERF/DATA/BUS/OPS), scores probability and impact, and defines mitigation plans for high-priority risks. - Prioritized Coverage Plan: Breaks acceptance criteria into P0-P3 scenarios across E2E, API, component, and unit levels with execution strategy and interval-based effort estimates. - Use Case: After drafting a PRD and architecture decision record for a new feature, run this Skill to produce a test design that flags architectural testability blockers and hands QA a concrete coverage plan. ## Quick Start Ask the AI to design a test plan for your epic or system based on 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 risk-based test plan for an epic?

Provide the epic or story documents with acceptance criteria, and the workflow detects epic-level mode automatically. It produces a single test design document with a risk matrix, P0-P3 coverage plan, execution order, and interval-based effort estimates.

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

System-level mode uses PRD plus ADR inputs and produces two documents: an architecture testability review and a QA execution recipe, plus a BMAD handoff file. Epic-level mode uses story acceptance criteria and produces one consolidated test plan per epic.

How are test priorities P0 through P3 assigned?

Priorities reflect business impact and workaround availability, not execution timing. P0 requires critical impact with no safe workaround, P1 covers core frequent behavior, P2 covers secondary behavior, and P3 covers rare or cosmetic cases. Risk scores are supporting evidence, not a mandatory condition.

Can I resume an interrupted test design workflow?

Yes. Each run writes a progress checkpoint named by run identity, such as test-design-progress-system.md or test-design-progress-epic-3.md. 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 test design?

System-level mode requires a PRD with functional and non-functional requirements, an ADR, and architecture documentation. Epic-level mode requires story markdown with clear acceptance criteria. The workflow halts and asks for missing prerequisites.