bmad-testarch-trace

Generates requirements-to-tests traceability matrices and deterministic quality gate decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lack visibility into which requirements are actually covered by tests and whether a story, epic, or release is safe to ship. This Skill maps acceptance criteria or inferred journeys to discovered 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 oracle items (acceptance criteria, OpenAPI endpoints, or synthetic user journeys) to E2E, API, component, unit, and live verification tests with FULL/PARTIAL/NONE/UNIT-ONLY/INTEGRATION-ONLY status. - Quality Gate Decision: Applies deterministic P0/P1 threshold rules over test results, coverage, NFR evidence, and waiver registers to emit gate-decision.json for CI/CD enforcement. - Gap Analysis & Recommendations: Prioritizes uncovered criteria into CRITICAL/HIGH/MEDIUM/LOW buckets with concrete Given-When-Then test suggestions. - Use Case: Before merging a release branch, run the workflow to discover that a P0 authentication criterion has only unit coverage, receive a FAIL gate decision, and get the exact test IDs needed to close the gap. ## Quick Start Ask the agent to create a traceability matrix and quality gate decision 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 tests?

Run the trace workflow, which resolves a coverage oracle from acceptance criteria, OpenAPI specs, or inferred user journeys, then maps each item to discovered tests by ID, describe block, and file path. The output is a traceability-matrix.md with per-criterion coverage status and gap analysis.

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 flaky test counts. The workflow writes gate-decision.json so pipelines can block or allow deployments automatically.

Can traceability work without formal acceptance criteria?

Yes. When no formal requirements exist, the workflow falls back to contract artifacts like OpenAPI specs, then external pointers, and finally a synthetic oracle that infers user journeys from routes, forms, and auth flows in the source code.

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_id, status pass, and a source_sha matching the commit under trace. Stale, failed, or unverifiable records become blockers instead.

When does the gate decision return FAIL?

The gate returns FAIL when any P0 criterion lacks FULL coverage, P0 test pass rate is below 100 percent, security issues exist, or flaky tests are detected. Security vulnerabilities cannot be waived under the waiver validity rules.