prd-review-panel

Reviews PRDs in parallel using seven sub-agent perspectives and synthesizes feedback.

1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/zacgoodwin/AIBootstrap --skill prd-review-panel-zacgoodwin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-review-panel
Source: https://github.com/zacgoodwin/AIBootstrap/tree/main/.claude/skills/prd-review-panel
Command: npx skills add https://github.com/zacgoodwin/AIBootstrap --skill prd-review-panel-zacgoodwin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product requirements documents often reach stakeholder review with unexamined assumptions, missing technical details, and unflagged legal or UX risks. This Skill runs a structured multi-perspective review of a PRD before that happens, surfacing blockers, gaps, and conflicting viewpoints in one synthesized report. ## Core Features & Use Cases - Seven parallel reviewer personas: Spawns Engineering, Design, Executive, Legal, UX Research, Skeptic, and Customer Voice sub-agents in a single parallel batch, each using its own review framework defined in .claude/agents/. - Stage-aware review focus: Adapts review emphasis to the PRD's lifecycle stage, from Team Kickoff through Launch Readiness. - Structured synthesis output: Produces a review-synthesis.md file categorizing feedback into Critical Blockers, Important Gaps, Enhancements, and Conflicting Perspectives, with action items and next steps. - Use Case: After drafting a PRD for a new onboarding flow, run the panel to get engineering feasibility concerns, legal privacy gaps, and a simulated customer reaction before your planning review meeting. ## Quick Start Ask the assistant to run /prd-review-panel on your latest PRD in outputs/prds/ to get a seven-perspective review with a synthesized report.

Frequently Asked Questions about prd-review-panel

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

FAQPage Schema
How do I review a PRD with multiple reviewer perspectives?

Run /prd-review-panel with an optional PRD name to spawn seven parallel sub-agents: Engineering, Design, Executive, Legal, UX Research, Skeptic, and Customer Voice. Each applies its own review framework, and results are merged into one synthesis document.

How to review only some perspectives of a PRD?

Pass the --perspectives flag with a comma-separated subset, such as --perspectives "eng,design,exec". Only the selected reviewer agents are spawned, and the synthesis covers just those viewpoints.

Where does the PRD review output get saved?

The synthesis is written to outputs/prds/[prd-name]-review-synthesis.md. It contains a TL;DR, critical blockers, important gaps, enhancements, conflicting perspectives, per-reviewer detail sections, and action items.

Does the PRD review adapt to different PRD stages?

Yes. The review focus shifts by stage: Team Kickoff emphasizes problem definition and strategic fit, Solution Review emphasizes technical approach and edge cases, and Launch Readiness emphasizes rollout, metrics, and compliance.

What happens when reviewers disagree on a PRD?

Disagreements are captured in a Conflicting Perspectives section stating each agent's position and rationale. The PM must make the call, and the skill suggests documenting the trade-off with a decision document.