bmad-testarch-trace

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

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-trace-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-trace
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-testarch-trace
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-trace-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often cannot tell which requirements are actually covered by tests or whether a release is safe to ship. 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, OpenAPI endpoints, or synthetically inferred user journeys to discovered E2E, API, component, unit, and live verification tests, classifying each as FULL, PARTIAL, NONE, UNIT-ONLY, or INTEGRATION-ONLY. - Gap Analysis & Quality Audit: Prioritizes coverage gaps by P0-P3 risk, detects duplicate coverage, missing error-path and auth negative-path tests, and flags test quality issues like hard waits or missing assertions. - Quality Gate Decision: Evaluates test pass rates, coverage thresholds, NFR status, and flakiness against deterministic rules to emit a gate decision with machine-readable JSON outputs for CI/CD pipelines. - Use Case: Before merging a release, ask the agent to analyze test coverage for a story; it produces a traceability matrix, an e2e-trace-summary.json, and a gate decision your pipeline can enforce. ## 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 and it auto-discovers tests by ID, describe blocks, and file patterns, then maps each requirement to tests across E2E, API, component, unit, and live levels. The output is a markdown traceability matrix plus a machine-readable JSON summary.

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 test pass rates, coverage thresholds, security issues, and flakiness. The workflow writes gate-decision.json so pipelines can block or allow deployments automatically.

Can traceability work without formal requirements documents?

Yes. When no formal acceptance criteria exist, the workflow resolves contracts like OpenAPI specs, follows external pointers to trackers, or infers synthetic user journeys from source code such as routes, forms, and auth flows.

Does the traceability workflow generate missing tests?

No. It only identifies coverage gaps and recommends specific test IDs, levels, and Given-When-Then scenarios. To create the missing tests, it directs you to run the companion ATDD or automate workflows.

How are live verification results counted as test coverage?

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