Skip to main content
skill CX Codex

bmad-tea-trace — Claude Code skill: coverage and setup

The bmad-tea-trace Claude Code skill maps requirements or journeys to tests, assesses coverage, and returns a quality gate decision. It activates for requests to build a traceability matrix or analyze test coverage.

MIT 863 installs ★ 118 updated 2026-11-13

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-trace -a claude-code
Open on GitHub

What bmad-tea-trace does

The skill links requirements or user journeys to tests, reviews coverage, then assigns the gate a PASS, CONCERNS, FAIL, or WAIVED status. It produces a Markdown traceability matrix plus JSON files for the test summary and gate decision.

Files go under {test_artifacts}/trace/, with a scope key in each filename, such as a story, epic, or release key. The project needs TEA configured in _bmad/config.toml, uv, and the bmod-tea skill installed alongside this one. The workflow stops if TEA is not configured or the sibling skill is missing from the same installation scope.

What it helps with

  • map requirements to tests
  • spot gaps in test coverage
  • produce a quality gate decision

Example prompts for the agent

  • Create a traceability matrix for this story.
  • Analyze test coverage for this release.
  • Validate the existing traceability outputs.

How to install bmad-tea-trace

1Skills CLI (Vercel)

npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-trace -a claude-code

2Manually: put the files in place

~/.claude/skills/bmad-tea-trace/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/bmad-tea-trace/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about bmad-tea-trace

How do I install bmad-tea-trace in Claude Code?

Run npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-tea-trace -a claude-code. The skill file is installed at ~/.claude/skills/bmad-tea-trace/SKILL.md.

What does bmad-tea-trace do?

It connects requirements or journeys with tests, evaluates coverage, and assigns a PASS, CONCERNS, FAIL, or WAIVED gate status. Its outputs include a traceability matrix and JSON summaries.

What does bmad-tea-trace need to run?

The project needs uv, TEA configured in _bmad/config.toml, and the bmod-tea skill installed beside it in the same scope. The workflow stops if either TEA setup or the sibling skill is missing.

Source text

SKILL.md · MIT
---
name: bmad-tea-trace
description: 'Generate traceability matrix and quality gate decision. Use when the user says "lets create traceability matrix" or "I want to analyze test coverage"'
---

# Coverage Traceability & Quality Gate

**Goal:** Generate a requirements-or-journeys-to-tests traceability matrix, analyze coverage, and make a quality gate decision (PASS / CONCERNS / FAIL / WAIVED).

**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}`.

## On Activation

Before resolving customizations or running hooks, inspect `{project-root}/_bmad/custom/` for `bmad-testarch-trace.toml` and `bmad-testarch-trace.user.toml`. If either 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`

**If the script fails**, resolve the `workflow` 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/{skill-name}.toml` — team overrides
3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides

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

### 1. Mode Determination

"Welcome to the workflow. What would you like to do?"

- **[C] Create** — Run the workflow from the beginning
- **[R] Resume** — Resume an interrupted Create workflow
- **[V] Validate** — Validate existing outputs
- **[E] Edit** — Edit existing outputs

### 2. Route to First Step

- **If C:** Load `{skill-root}/steps-c/step-01-load-context.md`
- **If R:** Load `{skill-root}/steps-c/step-01b-resume.md` (Create-mode continuation)
- **If V:** Load `{skill-root}/steps-v/step-01-validate.md`
- **If E:** Load `{skill-root}/steps-e/step-01-assess.md`

Create mode resolves the coverage oracle automatically in this order: formal requirements, contract/spec artifacts, resolvable external pointers (when `allow_external_pointer_resolution` is enabled), then synthetic journeys/requirements inferred from source (when `allow_synthetic_oracle` is enabled and no formal oracle exists).

Create mode resolves the gate target and a `run_key` (`story-{story_key}`, `epic-{epic_num}`, `release-{slug}`, `hotfix-{slug}`, or `system`) before its first save, and writes every output under `{test_artifacts}/trace/` with that key in the filename: `traceability-matrix-{run_key}.md`, `e2e-trace-summary-{run_key}.json`, and `gate-decision-{run_key}.json`. A run for one scope never reads or writes another scope's outputs.

© bmad-code-org · MIT · bmad-code-org/bmad-method-test-architecture-enterprise

Similar skills

All skills for Testing and QA →

From the same set10

The whole set →
bmod-tea The bmod-tea Claude Code skill stores the Test Architect module record. Run the bmad skill with setup tea to set up the module or check its state. CX Codex +1 1,000installs bmad-tea-automate 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. CX Codex +1 887installs bmad-tea-test-design The bmad-tea-test-design skill for Claude Code builds system-level and epic-level test plans grounded in risk assessment. CX Codex +1 882installs bmad-tea-test-review bmad-tea-test-review is a Claude Code skill that evaluates test quality against best practice standards. It triggers when you request a test suite audit or quality assessment. CX Codex +1 869installs bmad-tea-evaluate The bmad-tea-evaluate Claude Code skill runs behavioral evaluations of an agent and helps address gaps. It activates when asked to evaluate an agent or provide evidence that it behaves as expected. CX Codex +1 866installs bmad-tea-framework The bmad-tea-framework Claude Code skill sets up test frameworks and CI/CD for browser, backend, or mobile projects. It activates when asked to initialize or configure testing. CX Codex +1 861installs bmad-tea-nfr bmad-tea-nfr — a Claude Code skill that checks implementation evidence for performance, security, reliability, and maintainability. Start it by asking for an NFR review when implementation evidence is available. CX Codex +1 860installs bmad-tea-teach-me-testing bmad-tea-teach-me-testing is a Claude Code skill that teaches testing through guided sessions. It starts when someone asks to learn testing or test practices. CX Codex +1 850installs

Project sponsors

Companies that keep this analytics open