Prd Review
Review a product requirements document (PRD) or spec against a quality checklist and surface gaps, ambiguities, and risks before engineering starts. Use when the user says "review this PRD", "is this spec ready", "critique my requirements", "PRD checklist", or shares a doc and wants it pressure-tested before build.
Install
$ agentstack add skill-janellecipriano-pm-skills-prd-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-janellecipriano-pm-skills-prd-review) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
PRD Review
Pressure-test a PRD so problems are caught on the page, not in code. Be a constructive but skeptical reviewer.
When to use
- A PRD/spec exists and the user wants feedback or a readiness check before build/estimation.
To author a PRD from scratch, use a PRD-drafting workflow; this skill reviews an existing one.
Review checklist
Assess the doc against each dimension. Quote or reference specifics; don't be generic.
- Problem & why now — is the user problem clear and evidenced (not just a feature request)?
- Audience — are target users/segments and their context defined?
- Goals & success metrics — measurable outcomes, baseline → target? Anti-goals stated?
- Scope — explicit in/out? MVP vs. later cuts clear?
- Requirements — unambiguous, testable, prioritized (must/should/could)? No solution disguised as requirement.
- UX — flows, key states (empty/error/loading/edge), accessibility considered?
- Edge cases & failure modes — what happens when things go wrong?
- Dependencies & constraints — other teams, platforms, legal/privacy, performance.
- Risks & open questions — named, with owners.
- Measurement — instrumentation/analytics plan to know if it worked.
Process
- Read the PRD fully first.
- Rate each dimension: ✅ solid / 🟡 needs work / 🔴 missing — with a one-line reason.
- List the top gaps to fix before build, most important first.
- Pose the open questions the author must answer to be buildable.
- End with a verdict: Ready / Ready with fixes / Not ready.
Output format
A checklist table (dimension · rating · note), then Top gaps, Open questions, and the verdict. Be specific and kind; the goal is a better doc, not a teardown.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: janellecipriano
- Source: janellecipriano/pm-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.