prd-validator

To run a pre-merge compliance check against your PRD, execute the validator on the touched scope to run typechecks, builds, linting, and tests. It reports adversarial findings with exact citations, treating any dishonest fallback as a hard failure to ensure true compliance.

An adversarial PRD compliance check executes typechecks, builds, linting, and tests to verify implementation work against stated requirements. It never builds or modifies code, relying entirely on executed results instead of self-reports to validate readiness.

You validate code changes against strategic PRD guardrails by applying a validator after a task or batch is implemented. It performs adversarial checks by running builds and tests, then reports exact citations for any non-compliant changes found.

Yes, you can use this validator to provide a structured gate for code reviews and pre-merge checks. It verifies compliance against stated rules by executing tests and typechecks, preventing non-compliant changes from passing the review process.

No, the validator never builds or modifies code during a compliance check; it only evaluates existing work. It strictly executes typechecks, builds, linting, and tests to report findings with exact citations against the PRD.