Plan and spec traceability
Checks each requirement in a plan or specification against the implementation: done in this change, done elsewhere, or not started, with gaps graded by severity.
Sub-techniques
2
| ID | Name | Description |
|---|---|---|
V1053.001 | Requirement tracing | Link requirement ids to code and tests. |
V1053.002 | Gap analysis | Report where the implementation departs from the plan's intent. |
Craft it
- Write specs with stable requirement ids.
- Reference the ids in code comments or tests.
- Report untraced requirements and code with no requirement.
Reverse engineer it
Signs that a codebase already runs this technique, and where to read how it is configured.
- specs/ or docs/adr directories, requirement ids in tests.
Open-source packages
3
- Spec Kit github/spec-kit
- OpenFastTrace itsallcode/openfasttrace
- Instructor 567-labs/instructor