verify-spec

To validate that a spec matches a planning document, provide both document paths for comparison. The system checks intent reflection, requirement clarity, numeric consistency, system interactions, and verification readiness, returning a PASS or FAIL result.

Requirements validation is the process of checking a specification against a planning document for missing requirements, ambiguous expressions, numeric inconsistencies, and incomplete system interactions. It produces a PASS or FAIL judgment with a structured issue list and revision instructions.

To check numeric consistency and system interactions, pass the planning and specification file paths to the validator. It systematically compares formulas, behavior rules, and system interaction completeness across both documents, flagging mismatches in an issue list.

Yes, you can use automated spec review without external dependencies. The validator operates standalone, requiring only two document paths to compare feature requirements and behavior rules, generating PASS or FAIL results with concrete revision instructions.

The best way to get PASS or FAIL results for verification readiness is submitting both planning and spec paths to a validation workflow. It evaluates five checklist dimensions including verifier testability, then outputs a definitive judgment with actionable fixes.

A specification FAILS validation when it contains missing requirements, ambiguous expressions, numeric inconsistencies, or incomplete system interactions. The review identifies these gaps across five checklist dimensions and provides concrete revision instructions for the spec writer.