tracing-requirements-to-code
Builds and maintains bidirectional traceability between requirements and the tests that verify them: extracts a matrix from an existing codebase, annotates tests with requirement IDs, finds orphan tests and uncovered requirements, verifies that each link is real, and enforces linkage in CI. Use when a suite exists but nobody can say what it proves, when an auditor or stakeholder asks which tests cover a requirement, when a traceability matrix has gone stale, or when a requirement changes and its blast radius must be found. To plan coverage from a spec before tests exist, use requirements-test-coverage-mapper; to check whether one build is done, use verifying-acceptance-criteria.
Pinned to revision c4efc46815a7, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/tracing-requirements-to-code/SKILL.md
- skills/tracing-requirements-to-code/resources/extracting-an-rtm.md
- skills/tracing-requirements-to-code/resources/id-and-annotation-conventions.md
- skills/tracing-requirements-to-code/resources/orphan-and-drift-detection.md
- skills/tracing-requirements-to-code/resources/traceability-automation.md
Every link opens the file at its source, pinned to the revision this page describes.