PRD Compliance Validator

PRD compliance validation automatically scans your codebase against PRD mandates to verify implementations align with specified requirements. It dynamically extracts MUST USE and CANNOT USE directives from your PRD, then checks source code and configurations to ensure adherence before deployment, generating a compliance report identifying any violations.

Yes. This validator builds generic validation rules at runtime based on your PRD content, adapting to any requirement without requiring hardcoded tool names or patterns. Rules are dynamically generated from requirement extraction, enabling flexible compliance verification across different codebases and architectural contexts.

The validator acts as a post-implementation gate, blocking progression if violations are found. It generates a detailed .prd-compliance-report.json documenting all deviations, preventing costly errors before deployment and ensuring strict fidelity to your PRD's architectural and functional constraints.

The validator verifies compliance across codebases, configurations, and architectural boundaries by extracting requirements dynamically and applying generic rule-based verification. It checks for architecture constraints and component usage requirements regardless of your specific tech stack, making it adaptable to diverse implementations.

Run compliance validation after implementation is complete but before deployment. It serves as a critical validation gate that confirms all code adheres to PRD requirements, preventing deviations from reaching production and catching violations during development rather than in live environments.

The validator checks MUST USE components and technologies, CANNOT USE restrictions, and architecture constraints specified in your PRD. It performs implementation verification by scanning source code and configuration files to ensure presence or absence of specified elements and validates adherence to architectural mandates.