pm-review-board

Reviews PRDs and prototypes from six role perspectives with risk-graded findings.

187|12|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Luyu2026/Skill-Bible --skill pm-review-board-luyu2026
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-review-board
Source: https://github.com/Luyu2026/Skill-Bible/tree/main/pm-review-board
Command: npx skills add https://github.com/Luyu2026/Skill-Bible --skill pm-review-board-luyu2026

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product requirements often reach review meetings with hidden gaps in feasibility, testability, design states, tracking, or compliance, causing rework and launch incidents. This Skill simulates a multi-role review board that inspects your PRD, prototype, or requirement document before the real meeting and surfaces concrete, located, actionable issues. ## Core Features & Use Cases - Six-Role Parallel Review: Product, engineering, QA, UI/UX, operations, and legal/compliance perspectives each independently audit the material against detailed checklists. - Three Strictness Levels: Quick pass, standard review (default), or pre-launch final review where compliance, rollback, and acceptance issues are escalated to blockers. - Risk-Graded Output: Findings are merged, deduplicated, and classified as Blocker, Major, or Minor, producing a pass/conditional-pass/fail verdict plus a re-review checklist. - Use Case: Paste a PRD for a new checkout flow and receive a structured review report with located issues, per-role verdicts, rough dev/design effort estimates, and the exact fixes required before development starts. ## Quick Start Ask the AI to run pm-review-board on your PRD or requirement document and produce a multi-role review report with blocker, major, and minor findings.

Frequently Asked Questions about pm-review-board

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a PRD before a requirements meeting?▼

Submit your PRD, prototype, or requirement document and the Skill runs a six-role review covering product, engineering, QA, design, operations, and legal. It outputs a pass or fail verdict with risk-graded findings and specific fix suggestions.

What does a multi-role product requirements review check?▼

It checks requirement completeness, data and interface definitions, acceptance criteria, exception paths, interaction states, tracking and rollback plans, and privacy or content compliance. Each role applies its own checklist from the references directory.

Can I review a document from only one perspective like engineering?▼

Yes. If you ask for a single role's view, such as engineering feasibility or QA testability, the Skill outputs only that role's findings instead of the full six-role report, and notes that a complete review is available.

What happens if my PRD is too rough to review?▼

When material is only a few paragraphs or screenshots, the Skill does not force a full review. It outputs a material supplementation list and suggests generating a structured PRD first with a PRD-writing skill.

How are review findings prioritized in the report?▼

Findings are graded as Blocker, Major, or Minor. Any blocker produces a fail verdict; majors without blockers give conditional pass requiring fixes before testing; zero blockers and majors means the document passes into development.

When should I not use this review approach?▼

It is not suited for writing PRDs from scratch, pure code review, or pure design walkthroughs. Those tasks need dedicated writing, code-review, or design-critique skills instead.