Workflow: bmad-testarch-trace
Version: 5.0 (Step-File Architecture)
Create a coverage-oracle-to-tests traceability matrix, analyze coverage gaps, and optionally make a gate decision (PASS/CONCERNS/FAIL/WAIVED) based on evidence.
When formal requirements are unavailable, the workflow should resolve the best available coverage oracle automatically: specs/contracts first, external pointers second, and synthetic journeys/requirements inferred from source as the final brownfield fallback.
This workflow uses step-file architecture:
From workflow.yaml, resolve:
config_source, test_artifacts, user_name, communication_language, document_output_language, datetest_dir, source_dir, coverage_levels, gate_type, decision_modeLoad, read completely, and execute:
{skill-root}/steps-c/step-01-load-context.md
If the user selects Resume mode, load, read completely, and execute:
{skill-root}/steps-c/step-01b-resume.md
This checks the output document for progress tracking frontmatter and routes to the next incomplete step.