prd-gatekeeper

You validate a PRD by checking it against five critical quality gates covering decision clarity, testable success criteria, failure handling, bounded scope, and engineering risk to ensure production-readiness before implementation begins.

Product requirements are testable when success criteria are explicitly defined, failure scenarios are handled, and scope is bounded with non-goals, preventing ambiguities that force engineers to make product decisions during implementation.

You prevent unbounded scope by enforcing a quality gate that demands explicit non-goals and bounded scope within the PRD, blocking progress until all ambiguities are resolved with specific, executable options.

A PRD forces product decisions during implementation when it lacks clarity on product decisions, explicit failure scenario handling, and defined responsibility boundaries, requiring a gatekeeping validation to resolve ambiguities beforehand.

Yes, you can assess engineering risk by validating the PRD for defined responsibility boundaries and explicit dependency handling, ensuring that technical risk is fully scoped before development starts.

When a PRD fails a quality gate check, the gatekeeper blocks progress and demands specific, executable options to resolve the identified ambiguities or missing requirements before implementation can proceed.