bmad-tea

Provides a test architect persona for risk-based testing strategy and quality gate decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lack a dedicated test architecture perspective when planning test strategy, designing frameworks, or making release gate decisions, leading to flaky suites, poor coverage, and unquantified release risk. ## Core Features & Use Cases - Persona-Driven Test Advisory: Activates Murat, a Master Test Architect persona with customizable role, principles, and communication style via layered TOML configuration. - Test Strategy Workflows: Dispatches menu-driven workflows for test design, framework initialization, CI pipeline scaffolding, ATDD, test automation, test review, NFR assessment, and requirements-to-test traceability. - Knowledge-Backed Recommendations: Loads curated knowledge fragments covering API testing patterns, authentication sessions, Playwright utilities, Pact contract testing, and an ADR quality readiness checklist. - Use Case: Ask Murat to design a test strategy for a new epic, and the skill assesses risk, plans NFR coverage, and recommends API versus E2E test levels with concrete tooling mandates. ## Quick Start Ask Murat 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 workflow from the menu to run risk assessment, NFR planning, and coverage strategy at system or epic scope. The skill loads relevant knowledge fragments and maps requirements to prioritized test scenarios.

What testing tools does the test architect support?

It covers Playwright and Cypress for UI automation, pytest, JUnit, Go test, xUnit, and RSpec for service-layer tests, Pact for contract testing, and k6 for performance testing. CI guidance spans GitHub Actions, GitLab CI, Jenkins, Azure DevOps, and Harness.

Should I use API tests or E2E tests for backend validation?

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

Can I customize the test architect persona and menu?

Yes, customization merges base, team, and user TOML files where scalars override, arrays append, and menu items merge by code. You can adjust role, principles, persistent facts, and activation steps without changing the core identity.

How does the release gate decision workflow work?

The gate routes through optional test review and NFR evidence audit, then a trace phase that maps requirements to tests and issues a PASS, CONCERNS, FAIL, or WAIVED decision based on available evidence.