review-requirements

To validate REQUIREMENTS.md files for quality and traceability, audit the document against SB quality criteria by checking required sections, REQ-ID format, uniqueness, acceptance criteria, priority fields, and SPEC.md cross-references. This process reports structured PASS or ISSUES_FOUND findings without modifying the source document.

Acceptance criteria in requirements documents are testable when they include specific, verifiable conditions linked to a unique REQ-ID. The validation process checks for these strict frontmatter and content rules, ensuring each requirement has a priority field and traceability coverage to prevent gaps.

Checking SPEC.md criterion coverage involves cross-referencing each requirement in the document against the specifications. The artifact reviewer validates this traceability to ensure no duplicates or gaps exist across large projects, outputting structured PASS or ISSUES_FOUND findings.

Yes, you can audit requirements documents without modifying the original source file. The validation process applies strict frontmatter and content rules to read and evaluate the REQUIREMENTS.md file, reporting structured PASS or ISSUES_FOUND findings while preserving the source document exactly as is.

Validating REQ-ID format and uniqueness is necessary to prevent duplicate requirements and gaps across large projects. The artifact reviewer checks these identifiers along with traceability frontmatter and SPEC.md criterion coverage to ensure strict document quality and accurate cross-referencing.

Yes, the requirements validation process works for large projects by applying strict frontmatter and content rules to check cross-references to SPEC.md. It prevents duplicates or gaps across multiple specification files, reporting structured PASS or ISSUES_FOUND findings for artifact reviews.