Prd review gate
Book-learn-distill + Cursor Skills for PM workflow. Fork to clone PRD gates, issue-ready checks, and skill factory patterns.
npx -y skills add muqian2026-rgb/qian-public --skill prd-review-gateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
PRD completeness gate before dev: boundary → module breakdown → 95% review checklist. Triggers on "PRD review", "review this PRD", "PRD gate", "acceptance criteria check".
SKILL.md
2.0 KB, as published. Nobody here has run it
PRD Review Gate
Run a 95% completeness gate before engineering starts.
Source: distilled from a B2C mobile app PRD iteration process (de-identified).
When to use
- Before marking an Epic/Issue Ready for dev
- After PRD draft, before full design lock
- When QA keeps asking "what about edge case X?"
Five-stage production flow
| # | Stage | Output |
|---|---|---|
| 1 | Boundary | Scope in/out/deferred + user value + key assumptions; design sketch optional |
| 2 | Module breakdown | Tech modules (pages, APIs, data, permissions); enables parallel issues |
| 3 | Write by module | Single master PRD; one section per module |
| 4 | Second review (gate) | Checklist → target ~95% completeness before dev |
| 5 | Acceptance | Given–When–Then / scenario table aligned with QA matrix |
95% means: dev/QA rarely ask "this isn't written" — not word count.
Agent workflow
- Read the PRD (or section) the user points to.
- Walk references/checklist.md section by section.
- Output:
- Pass / Block with reason
- Missing items as a numbered list
- Suggested AC additions (draft bullets)
- Do not rewrite the whole PRD unless asked.
Document principles
| Principle | Rule |
|---|---|
| Single master PRD | One source of truth; no parallel PRD forks |
| Revision log | Optional footer: version, date, summary |
| Stable sections | Global rules → pages/scenarios → assets/API → acceptance |
Negative constraints
- Do not invent business numbers without source
- Do not replace TL architecture decisions
- Flag "out of scope" items explicitly if design shows them
Reference
Full checklist: references/checklist.md