speckit-adlc-product-validate

PRD validation compares feature specifications against the Product Requirements Document in a strict read-only pass. It checks scope, personas, success metrics, traceability, and boundary maps to identify misalignments and output a structured validation report.

PRD traceability verifies that feature specifications map directly to Product Requirements Document scope, personas, and metrics. Boundary mapping checks out-of-scope elements and demo sentences to ensure specs stay within defined project limits.

Yes, you can validate specs without modifying source files using a strict read-only validation pass. This approach enforces non-modification of original documents while surfacing actionable remediation guidance in a structured report.

A phase-driven PRD validation executes seven specific checks: scope, persona, metrics, traceability, out-of-scope, demo sentence, and boundary map. These checks load the PRD baseline to produce a comprehensive structured alignment report.

The best way to identify misalignments is comparing feature specifications against the PRD baseline using structured phase checks. This surfaces scope, persona, and metric discrepancies while providing actionable remediation guidance without altering files.

Yes, PRD validation works by targeting specs located under a designated specs directory or specific SPEC.md file. It loads the PRD baseline and traces specifications across phase checks to output a comprehensive validation report.