bmad-testarch-test-design

Design structured test plans from requirements and architecture documents.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-testarch-test-design-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-test-design
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-testarch-test-design
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-testarch-test-design-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design rigorous test strategies when they need to translate product requirements and architecture decisions into defensible QA plans. It reduces ambiguity by identifying risks, testability gaps, coverage priorities, and release gates before implementation moves too far.

Core Features & Use Cases

  • System-level test design: Review PRDs, ADRs, and architecture docs to produce architecture-facing and QA-facing test artifacts.
  • Risk assessment and prioritization: Classify risks by category, score their severity, and map them to mitigation plans and test coverage.
  • Coverage planning: Break requirements into P0-P3 scenarios, choose appropriate test levels, and define execution strategy and quality gates.
  • Workflow support: Generate, validate, resume, and edit structured test-design outputs using the workflow files and templates.
  • Use case: A team preparing a new backend feature can use this Skill to identify high-risk integrations, decide what must be tested first, and produce a QA plan that developers and testers can align on.

Quick Start

Ask for a system-level or epic-level test design for the feature, then provide the PRD, ADR, architecture notes, or epic/story requirements you want analyzed.

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 design a test plan from architecture and PRD documents?

To create a QA plan from architecture decisions, you identify risks, testability gaps, and coverage priorities to produce validation-ready artifacts. This Skill analyzes your PRDs and ADRs to generate prioritized scenarios, mitigation guidance, and execution strategy.

What is risk assessment and coverage strategy in epic-level testing?

Risk assessment in epic testing classifies risks by category and scores severity to map them to mitigation plans. Coverage strategy breaks requirements into P0-P3 scenarios, selects test levels, and defines execution strategy and quality gates.

How do I translate ADRs and architecture notes into QA planning artifacts?

Translating ADRs and architecture notes into QA planning artifacts requires mapping system decisions to testable scenarios and quality gates. This Skill processes your architecture documents to produce architecture-facing and QA-facing test design outputs.

Can I generate P0-P3 test scenarios for system-level features?

Yes, you can generate P0-P3 test scenarios for system-level features by providing PRDs, ADRs, or epic requirements. The Skill breaks down requirements into prioritized scenarios, selects appropriate test levels, and defines execution strategy.

Does this approach work for architecture review workflows?

Yes, this approach works for architecture review workflows by identifying testability gaps and coverage priorities before implementation moves too far. It produces architecture-facing test artifacts that help developers and testers align on high-risk integrations.

What's the best way to identify testability gaps before implementation?

The best way to identify testability gaps before implementation is to review PRDs and architecture docs to map risks to coverage plans. This Skill classifies risks by severity and maps them to mitigation plans and test coverage priorities.