bmad-testarch-trace

Generate requirements-to-tests traceability matrices and quality gate decisions for test coverage analysis.

Updated May 7, 2026
One-click install
npx skills add https://github.com/jgabriellima/deep-agent-skill --skill bmad-testarch-trace-jgabriellima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-testarch-trace
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/bmad-testarch-trace
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill bmad-testarch-trace-jgabriellima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lack visibility into which requirements are actually covered by tests, making release decisions risky and subjective. This Skill maps requirements or user journeys to existing tests, classifies coverage gaps by priority, and produces a deterministic PASS/CONCERNS/FAIL/WAIVED gate decision backed by evidence. ## Core Features & Use Cases - Traceability Matrix Generation: Maps acceptance criteria, API endpoints, or inferred user journeys to discovered tests across E2E, API, Component, and Unit levels, classifying each as FULL, PARTIAL, NONE, UNIT-ONLY, or INTEGRATION-ONLY. - Gap Analysis & Heuristics: Detects uncovered endpoints, missing auth negative-path tests, happy-path-only criteria, and UI journeys lacking E2E or state coverage, prioritized as CRITICAL/HIGH/MEDIUM/LOW. - Quality Gate Decision: Evaluates P0/P1 pass rates, coverage thresholds, security issues, and flakiness to emit a gate decision with machine-readable JSON outputs (e2e-trace-summary.json, gate-decision.json) for CI/CD pipelines. - Use Case: Before merging a story, run the workflow to discover that a P0 password-reset criterion has no error-path tests, receive a CONCERNS gate decision, and get concrete test recommendations with suggested test IDs. ## Quick Start Ask the agent to create a traceability matrix and analyze test coverage for the current story or release.

Frequently Asked Questions about bmad-testarch-trace

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

FAQPage Schema
How do I create a requirements traceability matrix for my tests?▼

Run the trace workflow, which auto-discovers tests in your test directory, maps them to acceptance criteria or inferred journeys, and outputs a traceability-matrix.md with coverage status per requirement. It classifies coverage as FULL, PARTIAL, NONE, UNIT-ONLY, or INTEGRATION-ONLY.

What is a quality gate decision in test coverage analysis?▼

A quality gate decision is a deterministic PASS, CONCERNS, FAIL, or WAIVED verdict based on P0/P1 test pass rates, coverage thresholds, security issues, and flakiness. The workflow emits gate-decision.json so CI/CD pipelines can block or allow deployments automatically.

Can traceability work without formal requirements documents?▼

Yes. When no formal requirements exist, the workflow resolves a coverage oracle from contract artifacts like OpenAPI specs, external pointers to trackers, or synthetic journeys inferred from source code such as routes, forms, and auth flows.

Does the traceability workflow generate missing tests?▼

No, it only identifies gaps and recommends specific tests with suggested IDs, levels, and Given-When-Then descriptions. To create the missing tests, it directs you to run the companion atdd or automate workflows.

What test levels does coverage analysis support?▼

The workflow supports E2E, API, Component, and Unit test levels, configurable via the coverage_levels variable. It calculates coverage percentages per level and flags unacceptable duplication across levels.