reviewing-requirements

To validate requirements and prevent drift, you provide a requirements document path or an ID. The tool loads the document, extracts references, verifies alignment, and outputs a structured findings report for remediation.

Reconciling test plans with requirements uses the test-plan reconciliation mode to ensure bidirectional traceability. It cross-references requirement artifacts against test plans after QA execution to identify coverage gaps.

Yes, you can check requirement alignment during a code review using the code-review reconciliation mode. It surfaces drift and gaps by cross-referencing the evolving software changes against the original requirements.

Yes, you need git and gh installed along with jq to review requirements. These dependencies are required for the scripts to extract references, verify documents, and cross-reference codebase artifacts.

The best way to keep documentation aligned with evolving software is running standard, test-plan, and code-review reconciliation workflows. This validates requirements across the lifecycle from planning to PR review.

Requirement verification cross-referencing a specific ID fails when the corresponding document or artifact cannot be loaded or located. The tool requires a valid file path or an exact ID to extract and verify references.