traceability-engine

The engine analyzes PRD content, test scenarios, and source files to map requirements to code and generate a traceability matrix. It outputs the matrix to the project reports directory and provides a gap summary for coverage validation.

Gap analysis identifies untested requirements, orphan tests, and stale traces by comparing PRD content against test scenarios and source files. It yields a gap summary in the project reports directory to support coverage validation and traceability auditing.

Yes, you can enforce end-to-end traceability using annotation-based mapping in code and tests. The engine analyzes these annotations alongside PRD content to detect untested requirements and orphan tests, writing the results to a traceability matrix.

Yes, the traceability engine supports risk scoring for test scenarios. It analyzes PRD content and test scenarios to surface gaps, calculate risk scores, and enforce end-to-end traceability from requirements to tests and source code.

The best way to audit requirement validation is to run the traceability engine, which maps PRD requirements to test scenarios and code. It detects coverage gaps and generates a traceability matrix and gap summary for audit trails in the reports directory.