bmad-tea-automate — Claude Code skill: what it does, how to install
The bmad-tea-automate skill generates tests in red or expand modes and runs and repairs new tests. The agent triggers it when users ask to automate tests or do ATDD.
MIT 887 installs ★ 118 updated 2026-11-13
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-automate -a claude-codeWhat bmad-tea-automate does
Operated under a test architect role, the skill coordinates with the sibling bmod-tea package and configuration files. Preflight routines validate local settings and resolve workflow routing before stepping through creation, validation, or editing workflows.
The setup relies on Python and uv to execute configuration scripts. Missing dependencies halt execution with prompts to install the required package scope and run setup routines.
What it helps with
- generate acceptance test scaffolds before implementation
- expand test coverage for existing code
- execute generated tests and fix defects
- verify project test architecture configuration
Example prompts for the agent
- automate tests for the latest changes
- expand test coverage for this module
- write acceptance tests for the feature
How to install bmad-tea-automate
1Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-automate -a claude-code2Manually: put the files in place
~/.claude/skills/bmad-tea-automate/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bmad-tea-automate/
1Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-automate -a codex2Manually: put the files in place
.agents/skills/bmad-tea-automate/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-automate -a cursor2Manually: put the files in place
.cursor/skills/bmad-tea-automate/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bmad-code-org/bmad-method-test-architecture-enterprise skills/bmad-tea-automate2Manually: put the files in place
.github/skills/bmad-tea-automate/SKILL.md1Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-automate -a gemini-cli2Platform CLI
gemini skills install https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise --path skills/bmad-tea-automateManually: put the files in place
.devin/skills/bmad-tea-automate/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-automate -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about bmad-tea-automate
How to install bmad-tea-automate in Claude Code?
Run npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-automate -a claude-code, then check ~/.claude/skills/bmad-tea-automate/SKILL.md.
What does bmad-tea-automate do?
It generates tests in red or expand modes, executes the test suite, and repairs broken tests automatically.
What is needed to run bmad-tea-automate?
You need the sibling bmod-tea skill installed in the same scope, uv available, and a valid _bmad/config.toml configuration file.
Source text
SKILL.md · MIT
---
name: bmad-tea-automate
description: 'Generate tests in red or expand mode and run-and-heal new tests. Use when the user says "lets expand test coverage", "I want to automate tests", "lets write acceptance tests", or "I want to do ATDD"'
---
# Test Generation: Red and Expand
**Goal:** Generate acceptance scaffolds before implementation in red mode, or expand passing coverage for implemented code in expand mode. Execute generated tests and repair confirmed test defects by default.
**Role:** You are the Master Test Architect.
You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
## Conventions
- Bare paths (e.g. `instructions.md`) resolve from the skill root.
- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
- `{project-root}` is the nearest folder containing `_bmad/`, starting at the project working directory and moving up through its parents.
- `{tea-knowledge}` is the `knowledge/` folder of the `bmod-tea` skill, installed beside this one: `{skill-root}/../bmod-tea/knowledge`. `tea-index.csv` there lists every fragment by a path relative to that folder.
- `{tea-contracts}` is the `contracts/` folder of the `bmod-tea` skill, installed beside this one: `{skill-root}/../bmod-tea/contracts`. `story-identity.md` there says how a story is resolved, read and named.
- `{skill-name}` resolves to the skill directory's basename.
- Resolve sibling workflow files such as `instructions.md`, `checklist.md`, `steps-c/...`, `steps-e/...`, `steps-v/...`, and templates from `{skill-root}`.
## Route Before Activation
Read `{skill-root}/resources/test-generation-routing.md` completely and resolve `test_mode`, `test_operation`, and `workflow-key` before executing activation.
Keep `{skill-root}` bound to this canonical directory throughout both modes.
The router selects exactly one customization key (`workflow` for expand, `workflow.red` for red); activation below uses that key only.
## On Activation
Before resolving customizations or running hooks, inspect `{project-root}/_bmad/custom/` for `bmad-testarch-automate.toml`, `bmad-testarch-automate.user.toml`, `bmad-testarch-atdd.toml`, `bmad-testarch-atdd.user.toml`, `bmad-tea-atdd.toml`, and `bmad-tea-atdd.user.toml`. Red settings live under `[workflow.red]` in `bmad-tea-automate.toml` and `.user.toml`; the atdd files are read nowhere. If any exists, stop and tell the user to run `npx --package=bmad-method-test-architecture-enterprise@4 tea-migrate-customizations --project-root {project-root}`. Resolve any reported manual merge, then start a fresh chat. Do not continue with default settings while legacy overrides remain.
### Step 1: Resolve the Workflow Block
Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key {workflow-key}`
The returned object is the `workflow` block for the rest of the run: `{workflow.activation_steps_prepend}`, `{workflow.persistent_facts}` and the other keys below read from it, whichever mode was selected.
**If the script fails**, resolve the block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
1. `{skill-root}/customize.toml` — defaults
2. `{project-root}/_bmad/custom/bmad-tea-automate.toml` — team overrides
3. `{project-root}/_bmad/custom/bmad-tea-automate.user.toml` — personal overrides
Then take the `workflow` table, or its `red` sub-table when `workflow-key` is `workflow.red`. Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
### Step 2: Execute Prepend Steps
Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
### Step 3: Load Persistent Facts
Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs resolved from `{project-root}` — expand them and load every matching file in lexical path order as facts. All other entries are facts verbatim.
### Step 4: Load Config
Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core --key modules.tea`. If the script fails, merge `{project-root}/_bmad/config.toml`, `{project-root}/_bmad/custom/config.toml` and `{project-root}/_bmad/custom/config.user.toml` yourself, in that order, with the merge rules above. If `_bmad/config.toml` is missing or has no `modules.tea` table, tell the user TEA is not set up, ask them to run `bmad setup tea` first, and stop.
Each `core` and `modules.tea` key is available as `{<key>}`, and as `config.<key>` in later steps. Replace `{project-root}` inside a value with the project root. Setup answers are strings: read `"true"` and `"false"` as booleans.
If `{tea-knowledge}/tea-index.csv` does not exist, the `bmod-tea` skill is not installed beside this one (`{skill-root}/../bmod-tea`). Tell the user to install `bmod-tea` in the same scope as this skill, and stop until it is there. For a skill in the project's skills folder run `npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmod-tea`; for a skill in the global skills folder add `-g`. Run the command on a yes. A headless run has no approval input: report the missing dependency and stop without running the installer. A `bmod-tea` installed in the other scope does not satisfy this skill.
### Step 5: Greet the User
Greet `{user_name}`, speaking in `{communication_language}`.
### Step 6: Execute Append Steps
Execute each entry in `{workflow.activation_steps_append}` in order.
Activation is complete. Begin the workflow below.
## Workflow Architecture
This workflow uses **tri-modal step-file architecture**:
- **Create mode (steps-c/)**: primary execution flow for new runs and resume continuation
- **Validate mode (steps-v/)**: validation against checklist
- **Edit mode (steps-e/)**: revise existing outputs
## Initialization Sequence
The router has already resolved the operation from the request.
For an interactive invocation that supplied no operation or generation intent, show Create, Resume, Validate and Edit once.
A generation intent starts Create; an autonomous invocation without an operation also starts Create.
Do not ask a second mode question.
Use `mode-prefix = red/` for red, or an empty prefix for expand:
- Create: load `{skill-root}/{mode-prefix}steps-c/step-01-preflight-and-context.md`.
- Resume: load `{skill-root}/{mode-prefix}steps-c/step-01b-resume.md`; continue its original `lastStep` mapping, scope and output path.
- Validate: load `{skill-root}/{mode-prefix}steps-v/step-01-validate.md`.
- Edit: load `{skill-root}/{mode-prefix}steps-e/step-01-assess.md`.
Resume restores Create progress; it does not start a new generation run.
Only Create terminals load `{skill-root}/resources/run-and-heal.md`.
Validate evaluates execution evidence as PASS/WARN/FAIL without repair or requiring a green suite.
Edit checks the requested changes only and never invokes automatic repair.
© bmad-code-org · MIT · bmad-code-org/bmad-method-test-architecture-enterprise