gov-traceability-manager

You validate traceability links by running validate_traceability.py against docs/traceability/links.yaml to verify link integrity across architecture, stories, tests, and release artifacts. The script identifies missing, stale, or orphaned references without silently repairing meaning.

Orphan report generation in traceability identifies missing, stale, or orphaned references across architecture, stories, tests, and release artifacts. It reports gaps rather than silently repairing meaning, ensuring deterministic checks after planning, verification, and deployment.

You generate a coverage report by running link_report.py to process link status and cross-reference release notes. The generator exports results to execution-plan/reports/req-coverage/generated-report.md, providing deterministic artifact coverage checks outside the model's free text.

Yes, you can use a YAML schema to maintain end-to-end traceability. This skill governs link integrity by validating the docs/traceability/links.yaml file, ensuring consistent change impact analysis and gap reporting across architecture, stories, tests, and release artifacts.

Yes, deterministic traceability validation applies deterministic checks after planning, verification, and deployment. It governs link integrity and checks release notes, evidence, and stories when shipped scope or verification changes occur in the project lifecycle.

Stale references appear in traceability coverage reports when shipped scope or verification changes break existing link integrity. Run the validator and report generator to update link status and identify the specific missing, stale, or orphaned references requiring cross-reference updates.