Purpose
Get comprehensive feedback on your PRD from 7 different perspectives in parallel: Engineering, Design, Executive, Legal, UX Research, Skeptic, and Customer Voice.
Catches gaps, challenges assumptions, and surfaces conflicts before stakeholder review.
Usage
/prd-review-panel- Review a PRD with all 7 sub-agents/prd-review-panel [prd-name]- Review specific PRD/prd-review-panel --perspectives "eng,design,exec"- Review with subset of agents
Context Routing
Check these files first:
thoughts/shared/pm/prds/- Active PRDs to reviewthoughts/shared/pm/sub-agents/- The 7 reviewer personasthoughts/shared/pm/frameworks/- Strategic context for executive reviewthoughts/shared/pm/- User research for UXR validation
Sub-agents available:
- engineer-reviewer.md - Technical feasibility, complexity, dependencies
- designer-reviewer.md - UX/UI feedback, user experience
- executive-reviewer.md - Strategic alignment, business impact
- legal-advisor.md - Compliance, risk, regulatory concerns
- uxr-analyst.md - User research synthesis, validation
- skeptic.md - Devil's advocate, challenge assumptions
- customer-voice.md - Simulate user perspective
Workflow
Step 1: PRD Selection
- If user specified PRD name:
- Look for it in
thoughts/shared/pm/prds/ - If found: Proceed
- If not found: List available PRDs, ask user to choose
- If no PRD specified:
- Scan
thoughts/shared/pm/prds/for recent PRDs (modified in last 30 days) - List them with:
- File name
- Title (from content)
- Last modified date
- Current stage (if indicated)
- Prompt: "Which PRD do you want to review?"
- Read the full PRD:
- Load complete content
- Note the current stage (Team Kickoff / Planning Review / XFN Kickoff / Solution Review / Launch Readiness)
- Identify sections present (some PRDs may be incomplete)
Step 2: Review Preparation
Extract key elements from PRD:
- Problem statement - What user pain are we solving?
- Hypothesis - If we build X, then Y will happen because Z
- Strategic fit - Why this vs other things?
- Non-goals - What's explicitly out of scope?
- Success metrics - How we measure success
- Rollout plan - A/B test or full launch?
- Technical approach - How we'll build it (if specified)
- UX design - Mockups, flows, behavior examples
- Stakeholders - Who needs to approve/support
- Risks - Known concerns or open questions
Determine review focus based on stage:
- Team Kickoff stage: Focus on problem definition, strategic fit
- Planning Review stage: Focus on scope, estimates, prioritization
- XFN Kickoff stage: Focus on cross-functional alignment, dependencies
- Solution Review stage: Focus on technical approach, UX design, edge cases
- Launch Readiness stage: Focus on rollout plan, metrics, compliance
Step 3: Spawn 7 Sub-Agents in Parallel
CRITICAL: Use single message with multiple Task tool calls for parallel execution.
For each sub-agent, create Task with:
Agent 1: Engineering Reviewer
Prompt:
You are an engineering reviewer. Review this PRD for technical feasibility.
PRD Content:
[Full PRD text]
Review framework:
1. Technical Feasibility
- Is the proposed solution technically sound?
- Are there better technical approaches?
- What's the complexity (S/M/L/XL)?
2. Dependencies & Integration
- What systems/services does this touch?
- What dependencies are missing from the PRD?
- What could break?
3. Scalability & Performance
- Will this scale to expected load?
- What performance concerns exist?
- What monitoring is needed?
4. Edge Cases & Error Handling
- What edge cases aren't addressed?
- How should errors be handled?
- What failure modes exist?
5. Timeline & Estimates
- Are engineering estimates realistic?
- What's missing from the estimate?
- What unknowns could cause delays?
Provide:
- ✅ What looks good technically
- ⚠️ Concerns or gaps
- ❌ Blockers or red flags
- 💡 Suggestions for improvement
Be specific. Reference line numbers or sections of the PRD.
Agent 2: Design Reviewer
Prompt:
You are a design reviewer. Review this PRD for user experience.
PRD Content:
[Full PRD text]
Review framework:
1. User Experience
- Is the proposed UX intuitive?
- Are there better interaction patterns?
- What friction points exist?
2. Visual Design
- Do mockups align with design system?
- Are UI patterns consistent?
- Is information hierarchy clear?
3. Accessibility
- Are accessibility requirements specified?
- Can all users complete the flow?
- What a11y concerns exist?
4. Edge Cases in UX
- Error states defined?
- Loading states clear?
- Empty states addressed?
5. User Research Validation
- Is this validated with users?
- What assumptions need testing?
- Are there usability risks?
Provide:
- ✅ Strong UX decisions
- ⚠️ Usability concerns
- ❌ UX blockers
- 💡 Design improvements
Be specific about which flows or screens have issues.
Agent 3: Executive Reviewer
Prompt:
You are an executive reviewer. Review this PRD for strategic alignment and business impact.
PRD Content:
[Full PRD text]
Strategic Context:
[Include content from thoughts/shared/pm/frameworks/ if available]
Review framework:
1. Strategic Alignment
- How does this support company strategy?
- Does it advance key metrics (North Star, OKRs)?
- Why this vs other opportunities?
2. Business Impact
- What's the expected ROI?
- How does this affect revenue/growth/retention?
- What's the opportunity cost?
3. Prioritization
- Is this the right thing to build now?
- What else could the team be working on?
- What's the urgency/importance trade-off?
4. Market & Competitive
- How does this position us vs competitors?
- What market need does this address?
- What's the differentiation?
5. Resource Allocation
- Is the team/time investment justified?
- What other initiatives does this affect?
- Should we staff this differently?
Provide:
- ✅ Strategic strengths
- ⚠️ Strategic concerns
- ❌ Misalignment with strategy
- 💡 Strategic recommendations
Think like a VP or C-level executive reviewing this for approval.
Agent 4: Legal Advisor
Prompt:
You are a legal/compliance reviewer. Review this PRD for risk and regulatory concerns.
PRD Content:
[Full PRD text]
Review framework:
1. Privacy & Data
- What user data is collected/stored/processed?
- Are privacy requirements specified (GDPR, CCPA)?
- Is data retention addressed?
2. Compliance & Regulations
- What regulations apply (industry-specific)?
- Are compliance requirements called out?
- What legal reviews are needed?
3. Security
- What security considerations exist?
- Are security requirements specified?
- What attack vectors should be considered?
4. Contracts & Terms
- Does this affect user agreements/ToS?
- Are B2B contract implications considered?
- What legal language is needed?
5. Risk Assessment
- What legal risks exist?
- What liability concerns apply?
- What could go wrong legally?
Provide:
- ✅ Legal considerations addressed
- ⚠️ Legal/compliance gaps
- ❌ Legal blockers or high-risk items
- 💡 Risk mitigation recommendations
Flag anything that needs legal team review before proceeding.
Agent 5: UX Research Analyst
Prompt:
You are a UX research analyst. Review this PRD for research validation and user insights.
PRD Content:
[Full PRD text]
User Research Context:
[Include recent research from thoughts/shared/pm/ if relevant]
Review framework:
1. Research Validation
- What user research supports this?
- Are assumptions validated or just assumed?
- What evidence backs the problem statement?
2. User Needs
- Does this solve a real use