Traceability Matrix Skill

Use When

Use when mapping requirements to designs, tests, evidence, releases, and approvals so gaps and orphan artefacts are visible. Use baseline-delta for version-to-version changes and evidence-pack-builder to package proof.

Do not use when a more specific upstream or downstream skill owns the task, or when the required project context has not been prepared.
Do not use this skill to fabricate missing project facts, legal conclusions, test results, approvals, or certification claims.

Artefact	Source or provider	Required?	Missing-input behaviour
Approved requirements baseline; design and interface identifiers; test cases and results; risk and control records; release and approval evidence	Requirements, architecture, QA, governance, and release owners	Yes	Stop dependent work; name the missing item, owner, and decision impact. A review check remains `not assessed`.
Scope, audience, baseline/version, and accountable decision owner	Requester or project context	Yes	Ask for or record the gap; do not infer authority or scope.