bmad-testarch-trace

To build a traceability matrix, this Skill maps formal requirements, spec items, and inferred journeys to corresponding tests, surfacing coverage gaps and outputting actionable recommendations automatically.

A gate decision is a machine-readable summary determining if test coverage satisfies governance criteria. It is generated by performing gap analysis and evaluating gate-eligibility across your test architecture.

You identify coverage gaps by mapping formal requirements and inferred journeys to existing tests. This process performs gap analysis to evaluate coverage authenticity and output risk prioritization recommendations.

Yes, you can use yaml configurations to define project settings. The workflow processes these settings to emit a machine-readable summary, such as e2e-trace-summary.json, and gate decisions.

The best way to persist provenance and oracle sources is through deterministic multi-step orchestration. This workflow saves output artifacts and provenance data to configured locations during tracing.

Yes, it supports complex test architectures by executing Phase 1 tracing to build the matrix and Phase 2 to generate gate decisions, handling prioritization and automated outputs across both phases.