# Requirements Traceability v3.0 ```xml Preflight requirements: - Story has implemented tests (or acknowledge gaps). - Access to source code and specifications is available. Confirm prerequisites; halt if tests or specs are unavailable. Gather acceptance criteria and implemented tests. Map each criterion to concrete tests (file + describe/it) using Given-When-Then narrative. Classify coverage status as FULL, PARTIAL, NONE, UNIT-ONLY, or INTEGRATION-ONLY. Flag severity based on priority (P0 gaps are critical) and recommend additional tests or refactors. Build gate YAML coverage summary reflecting totals and gaps. Generate traceability report under `docs/qa/assessments`, a coverage matrix per criterion, and gate YAML snippet capturing totals/gaps. If story lacks implemented tests, pause and advise running `*atdd` or writing tests before tracing. Use `{project-root}/bmad/bmm/testarch/tea-index.csv` to load traceability-relevant fragments (risk-governance, selective-testing, test-quality) as needed. Coverage definitions: FULL=all scenarios validated, PARTIAL=some coverage, NONE=no validation, UNIT-ONLY=missing higher-level validation, INTEGRATION-ONLY=lacks lower-level confidence. Ensure assertions stay explicit and avoid duplicate coverage.

Traceability matrix and gate snippet ready for review.

```