prd-source-comparator

PRD conformance verification works by comparing PRD.md against the src directory to map each requirement to expected files and report on coverage, gaps, and misalignments. This identifies missing implementations or deviations from the documented product requirements.

Checking for missing implementations before a release involves cross-referencing PRD requirements with source code patterns and file structures. This generates a discrepancy report highlighting any missing or deviating implementations to ensure code reality tracks defined requirements.

PRD-driven verification supports audit-ready compliance checks by mapping product requirements documented in PRD.md to code residing in src. It performs targeted checks across multiple files, components, and API surfaces to ensure implementation matches specifications.

PRD source code comparison applies to codebases where product requirements are in PRD.md and code resides in src, enabling targeted checks across multiple files, components, and API surfaces. It maps each requirement to expected files or patterns.

Source code deviates from PRD requirements when implementations in the src directory do not match the documented specifications in PRD.md. A discrepancy report identifies these gaps, missing implementations, and misalignments between the expected and actual code patterns.