traceability-check

Requirements traceability automatically maps your documented requirements (UC-*, REQ-*, NFR-*) to implementation code and test coverage, then identifies gaps. It scans requirement files, code comments and annotations, and tests to build a bidirectional matrix showing which requirements are implemented and tested.

Yes. The traceability check identifies orphan requirements with no code implementation, untested requirements lacking test coverage, and code files with no requirement links. It generates a gap report showing coverage percentages and specific artifacts missing bidirectional links.

Traceability coverage analysis recognizes UC-*, REQ-*, and NFR-* requirement ID formats stored in .aiwg/requirements. It scans code for these IDs in comments, annotations, and commit messages, then matches them against test coverage to compute bidirectional traceability.

Yes. Traceability analysis requires a software project with documented requirements in standardized formats (UC-*, REQ-*, NFR-*) plus corresponding code and test artifacts. Without requirement documentation, the tool cannot establish the bidirectional mapping needed for gap detection.

The report shows total requirements counted, implementation percentage, test coverage percentage, and specific gaps: orphan requirements lacking code, untested requirements, and code files without requirement links. Output is a markdown report with statistics and actionable recommendations.

By identifying rogue code features with no linked requirements and requirements with no implementation or tests, traceability analysis prevents untracked scope additions and ensures complete coverage. Gap reports highlight which artifacts break bidirectional traceability, enabling teams to close coverage systematically.