bmad-tea

Guides risk-based test architecture, automation strategy, and quality gate decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams struggle to design coherent testing strategies across API, UI, contract, and performance layers, often ending up with flaky E2E suites, unclear coverage, and release decisions made without evidence. This Skill provides a Master Test Architect persona that applies risk-based testing principles and structured quality gates to every testing decision. ## Core Features & Use Cases - Test Design & Risk Assessment: Produces risk assessments, NFR planning, and coverage strategies for systems or epics, including a 29-criteria architecture readiness checklist. - Test Automation & Frameworks: Scaffolds production-ready test frameworks, generates prioritized API/E2E tests with fixtures, and supports Playwright, Cypress, Pact, k6, pytest, JUnit, and Go test. - Quality Gates & Traceability: Maps requirements to tests, audits NFR evidence, and issues PASS/CONCERNS/FAIL/WAIVED release gate decisions. - Use Case: Ask the Test Architect to design tests for a new epic; it assesses risk, plans API-first coverage, generates failing ATDD acceptance tests, and later traces requirements to tests for a release gate decision. ## Quick Start Ask Murat the Test Architect to design a risk-based test strategy for your current epic or feature.

Frequently Asked Questions about bmad-tea

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a risk-based test strategy for an epic?

Invoke the Test Design capability, which produces a risk assessment, NFR planning, and coverage strategy scoped to a system or epic. It prioritizes scenarios by impact and prefers lower test levels like unit and API tests over E2E where possible.

What testing frameworks does the Test Architect support?

It supports Playwright and Cypress for browser E2E, Pact for consumer-driven contract testing, k6 for performance and load testing, and pytest, JUnit, Go test, xUnit, and RSpec for API and service-layer testing across major CI platforms.

Should I use API tests or E2E tests for business logic?

Use API tests for CRUD operations, business logic, error handling, and data validation since they run faster and are more stable. Reserve E2E tests for user journeys, visual regression, and cross-browser concerns.

How does the release quality gate decision work?

The gate workflow traces requirements to tests, optionally audits test quality and NFR evidence, then issues a PASS, CONCERNS, FAIL, or WAIVED decision. It routes to the correct sub-workflow based on which evidence artifacts already exist.

Can it generate acceptance tests before development starts?

Yes, the ATDD capability generates failing acceptance tests plus an implementation checklist before development begins. This anchors the team on executable acceptance criteria derived from the story or feature.