prd-review

Coordinate multi-pass PRD reviews to surface prioritized gaps and inconsistencies.

11|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill prd-review-thrawn01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-review
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/prd-review
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill prd-review-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams quickly identify gaps, inconsistencies, and ambiguities in a PRD by coordinating multi-pass reviews that surface actionable issues for the next steps.

Core Features & Use Cases

  • Multi-pass PRD review: four agent passes (review, validation, skeptic, fix proposal) to surface findings and recommended edits.
  • Cross-reference: PRD, tech spec, ADRs, and CONTEXT glossary for consistency and scope alignment.
  • Actionable outputs: concrete PRD edits, rationale, and recommended next steps to resolve gaps.

Quick Start

Run the PRD-review skill to initiate iterative, four-pass analysis and surface actionable changes.

Frequently Asked Questions about prd-review

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

FAQPage Schema
How do I identify gaps and ambiguities in a PRD before tech spec creation?

To identify gaps in a PRD, coordinate a multi-pass review across PRD sections, ADRs, and CONTEXT glossary to surface inconsistencies and ambiguities. This process prioritizes findings with P0, P1, or P2 levels to drive product decisions.

What is the best way to review a PRD for scope drift and inconsistencies?

The best way to review a PRD for scope drift is applying a four-pass analysis: review, validation, skeptic, and fix proposal. This cross-references tech specs and ADRs to surface actionable findings and concrete edits for resolution.

How does multi-agent PRD gap analysis work?

Multi-agent PRD gap analysis works by executing four iterative passes: review, validation, skeptic, and fix proposal. It cross-references the PRD, ADRs, and CONTEXT glossary to output concrete edits, rationale, and recommended next steps.

Can I cross-reference ADRs and a CONTEXT glossary during a PRD review?

Yes, you can cross-reference ADRs and a CONTEXT glossary during a PRD review. The multi-pass analysis checks these documents alongside the tech spec to ensure scope alignment and surface actionable inconsistencies for resolution.

How do I prioritize PRD review findings for the engineering team?

You prioritize PRD review findings by assigning P0, P1, or P2 severity levels to identified gaps and ambiguities. This provides concrete PRD edits and user questions to drive product decisions and resolve scope issues efficiently.

What are the limitations of automated PRD consistency checks?

Automated PRD consistency checks are limited to surfacing actionable findings and proposing fixes based on existing documents. They cannot make final product decisions; they output concrete edits and user questions for human resolution of gaps.