bmad-testarch-trace

To generate a traceability matrix linking requirements to tests, the workflow loads your story inputs and test artifacts to automatically map coverage and output a Markdown traceability report.

Requirements-to-tests gap analysis evaluates coverage across priority levels to identify missing tests and risk signals, producing actionable recommendations to support deployment gate decisions.

You can automate a gate decision by running the workflow to analyze test coverage gaps and risk signals, which saves a Phase-1 matrix to a temp file to support the Phase-2 deployment decision.

Yes, you need to load existing test artifacts and knowledge fragments as inputs so the workflow can accurately map them against your story requirements and detect coverage gaps.

The best way to analyze test coverage gaps across priority levels is to use an automated traceability workflow that cross-references story requirements with test artifacts to highlight risk signals.