bmad-testarch-trace

Generate requirements-to-tests traceability matrices and quality gate decisions.

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

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 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, OpenAPI endpoints, or synthetically inferred user journeys to discovered tests across E2E, API, component, unit, and live verification levels. - Gap Analysis & Quality Checks: Identifies uncovered P0-P3 criteria, duplicate coverage, missing error-path and auth negative-path tests, and test quality issues like hard waits or missing assertions. - Quality Gate Decision: Applies deterministic threshold rules to test results, coverage, NFR evidence, and flakiness data, emitting CI/CD-consumable JSON outputs (e2e-trace-summary.json, gate-decision.json). - Use Case: Before merging a release, run the workflow to confirm 100% P0 coverage, detect that a password-reset flow lacks error-path tests, and block deployment until the gap is fixed. ## 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 test coverage?

Run the trace workflow, which resolves a coverage oracle from acceptance criteria, specs, or inferred journeys, discovers tests by ID and level, and maps each requirement to its tests. The output is a traceability-matrix.md with coverage status per criterion.

What is a quality gate decision in CI/CD testing?

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

Can traceability work without formal requirements documents?

Yes. When no formal oracle exists, the workflow can resolve contracts like OpenAPI specs, follow external pointers to trackers, or infer synthetic user journeys from source code routes, forms, and auth flows, assigning provisional P0-P3 priorities.

How are live verification results counted as test coverage?

Live results are read from a live-verification-results.json file and count as coverage only when the record has a unique ID, a recognized requirement, status pass, and a source SHA matching the commit under trace. Stale, failed, or unverifiable records become blockers.

What happens when P0 coverage is below 100 percent?

A P0 coverage gap is classified as a CRITICAL blocker and forces a FAIL gate decision unless formally waived with a named approver, expiry date, and remediation plan. Security vulnerabilities can never be waived.