prd-review

PRD Review

This skill performs a deep PRD and requirements quality audit. It is for understanding and challenging the business logic in a requirement document, not for checking whether a document follows a fixed template.

Core Intent

Review whether the requirement is correct, clear, consistent, complete, implementable, and testable.

Before criticizing, build a business understanding:

• Business goal and system boundary
• Actors, roles, and permissions
• Business objects and data relationships
• Module responsibilities and module boundaries
• Core workflows and state transitions
• Cross-module dependencies and side effects
• Normal, exception, boundary, retry, rollback, and audit rules

Distinguish explicitly between:

• Stated: directly present in the source document
• Inferred: reasonable inference from the document
• Missing: required for implementation or testing but absent
• Question: must be confirmed by product/business owner

When To Use

Use this skill when the user asks to:

• Deeply review a PRD or requirement document
• Find business logic errors, omissions, contradictions, or ambiguity
• Evaluate module relationships, internal rules, and cross-module flows
• Check whether developers and testers can implement and verify the requirement
• Produce detailed modification advice, not just a score

Do not use this as the primary skill when the user only wants grammar cleanup, document formatting, or a fixed delivery checklist review.

Required Workflow

1. Ingest source material

   • Read the user-provided document(s), preserving section names and locations.
   • For DOCX/PDF inputs, extract text with the appropriate document tooling.
   • Note unreadable diagrams, external links, missing attachments, or image-only flowcharts.

2. Load review framework

   • Read references/review-framework.md before the first substantive review.
   • Read references/issue-taxonomy.md before classifying findings.
   • Read references/report-template.md before writing the final report.
   • Read additional reference files only when needed:
     • references/module-review-template.md for per-module review.
     • references/cross-module-checklist.md for module interaction and consistency checks.
     • references/business-rule-checklist.md for rules, states, data, permission, and exception checks.
     • references/requirement-quality-checklist.md for clarity, consistency, priority, terminology, data definition, and ambiguity checks.