Skip to main content
The traceability matrix uses stable in-repository references to answer two questions: which feature implements each requirement, and which check verifies each acceptance criterion.

Reference chain

A feature’s source_refs can reference a requirement directly or an acceptance criterion in a user story. Each verification’s source_refs should point to the acceptance criteria it actually verifies.

View the matrix

See the traceability command → The command outputs the matrix and gaps as JSON and returns a nonzero exit code when the matrix is incomplete. status also includes a traceability summary.

Common gaps

Traceability checks are deferred while template scope placeholders have not been decomposed. After real requirements and features exist, gaps become [traceability] errors in validate.
Each verification should reference only the acceptance criteria it actually demonstrates. Do not attach every AC to one broad command just to make the matrix green.