Verification · Intent and spec conformance · Plan and spec traceability
Requirement tracing
Link requirement ids to code and tests.
How to build it
- Give each requirement in the spec a stable id.
- Add that id to the code comment or test name that implements it.
- Run the tracing tool in CI and fail on requirements with no link.
Signals in a repository
- Requirement ids in spec files that tests and code comments reference.
- A specs/ or docs/adr directory with numbered requirement files.
- A CI step that runs OpenFastTrace over the spec and source directories.
In practice
No scanned repository runs a tool for this check. The steps above are the only guidance.