PRD Reviewing

Purpose

Systematically review Product Requirements Documents to ensure they are complete, clear, actionable, and ready for implementation planning. Identifies issues before they become costly engineering problems.

When NOT to Use This Skill

• Creating PRDs (use prd-writing instead)
• Reviewing technical implementation plans (use sparc-planning or technical-spec-reviewing)
• Code review (different domain entirely)
• No PRD exists yet (nothing to review)
• Reviewing feature specs (use feature-spec-reviewing instead)

Review Workflow

Step 1: Document Analysis

Read the entire PRD and assess structural completeness: