review-all-prds

Aggregate MVP PRDs to detect cross-PRD contradictions and gaps.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill review-all-prds
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-all-prds
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/review-all-prds
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill review-all-prds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Holistic cross-PRD review reads every PRD together to identify contradictions, misalignments, and gaps that single-PRD reviews miss, enabling proactive resolution before architecture work begins.

Core Features & Use Cases

  • Build cross-PRD summaries including a screen-by-screen map, a centralized event vocabulary, and a catalog of configurable values.
  • Detect cross-system flows, permission timing issues, and background-work overlaps to surface conflicts early.
  • Provide a printed report of findings to guide decisions and escalation paths before design-system retrofit or architecture.
  • Read-only. Produces a printed report. The user runs specific commands to resolve findings.

Quick Start

Run the holistic PRD review after all MVP PRDs are approved to surface cross-PRD contradictions.

Frequently Asked Questions about review-all-prds

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

FAQPage Schema
What is a cross-PRD review and how does it detect conflicts across product requirements?▼

A cross-PRD review aggregates all approved product requirement documents to detect contradictions in screens, flows, permissions, analytics, and timing. It builds cross-PRD summaries and a centralized event vocabulary to surface misalignments early.

How do I check cross-PRD consistency before starting architecture work?▼

To check cross-PRD consistency, run a holistic review after all MVP PRDs are approved. It reads your design artifacts, maps cross-system flows, checks permission timing, and outputs a printed report with prioritized findings to guide architecture.

When do I need to perform a holistic product requirements document gap analysis?▼

You need a holistic PRD gap analysis when many MVP PRDs exist and you must verify consistency across screens, flows, permissions, analytics, and timing. It identifies misalignments that single-PRD reviews miss before design-system retrofit begins.

Can I resolve cross-PRD conflicts automatically within the review report?▼

You cannot resolve cross-PRD conflicts automatically. The review is read-only and produces a printed report of prioritized findings to guide decisions. Users must run specific commands externally to resolve the identified conflicts and gaps.

What limitations exist when detecting cross-system flow and background-work overlaps?▼

The primary limitation is its read-only nature; it only detects cross-system flows, permission timing issues, and background-work overlaps to surface conflicts early. It outputs a report but does not execute resolution commands or modify the design artifacts directly.