Review a Product Requirements Document

Purpose

Audit a PRD the way an experienced product reviewer would: surface the gaps that cause planning churn, rework, and post-launch surprises.

Shared Operating Model

Use requirements-operating-model before reviewing. Use it to check module boundaries, source-of-truth conflicts, clarification needs, and likely downstream Blueprint / Work Order impact.

When to Use

• Review a PRD draft before sharing it for sign-off
• Audit an existing PRD against current state
• Get a second opinion on a spec written by someone else
• Pre-flight a PRD for an engineering planning session

Project Identifier