| name | review-prd |
| type | atomic |
| license | MIT |
| description | Review a PRD for completeness, testability, clarity, feasibility, scope, dependencies, and edge cases — classify findings as Critical/Suggestion/Note, cite specific sections, and provide a verdict. Use when reviewing a PRD, PRD review, validate PRD, feasibility check. |
| metadata | {"version":"1.0.0","user-invocable":"true"} |
Reviewing a PRD
Evaluate a PRD for quality — not agreement with a preferred solution.
HARD-GATE
- Review the document, not the idea.
- Every finding must cite a specific PRD section (redact sensitive data).
- No alternative solutions unless a requirement is infeasible.
Core Process
- Receive the PRD.
- Apply the review checklist (completeness, testability, clarity, feasibility, scope, dependencies, edge cases).
- Classify each finding as Critical, Suggestion, or Note.
- Produce a findings table with severity, evidence, and recommendation.
- Verdict: Approved / Approved with Suggestions / Needs Revision.
- If Needs Revision, instruct author to address Critical findings and re-run review.
Output
- Verdict.
- Findings table with columns: #, Severity, Section, Finding, Evidence, Recommendation.
- Summary with count by severity.
- Acknowledgement of well-written sections.
Review Checklist (abbreviated)
Completeness: goals and success metrics are measurable; out-of-scope explicit.
Testability: requirements can be verified with pass/fail tests; acceptance criteria are specific.
Clarity: no undefined jargon; no ambiguous modal verbs.
Feasibility: timeline realistic; dependencies identified.
Scope & Edge Cases: failure scenarios described; migration/compatibility concerns.
Refer to the full checklist in the skill’s reference documentation.
Integration
| Skill | When |
|---|
| create-prd | Review immediately after PRD generation |
| generate-tasks | After review passes |
| tech-lead persona | For deeper feasibility assessment |
