prd-review

Analyze product requirement documents for missing, weak, or inconsistent content.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill prd-review-infraspecdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-review
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/general/prd-review
Command: npx skills add https://github.com/infraspecdev/tesseract --skill prd-review-infraspecdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reviews product requirement documents before implementation to surface missing decisions, vague scope, weak metrics, rollout risks, compliance gaps, and other issues that can derail delivery.

Core Features & Use Cases

  • Parallel multi-dimension review: Evaluates a PRD across problem framing, scope, success metrics, scenarios, approvals, legal and privacy, rollout, support impact, risks, and cost.
  • Severity-based scoring: Converts findings into graded gaps with P0, P1, and P2 severity so teams can prioritize what blocks delivery versus what is merely nice to improve.
  • Enhanced PRD output: Produces a revised version of the PRD with suggested fixes and machine-readable review artifacts for downstream workflows.
  • Use case: A product manager can paste a draft PRD or point the Skill at a file or URL to get a structured gap analysis before handing it to engineering.

Quick Start

Ask this Skill to review your PRD and return a scored gap analysis with prioritized fixes.

Frequently Asked Questions about prd-review

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

FAQPage Schema
How do I review a PRD for missing requirements before engineering starts?

Find PRD gaps before implementation by running a parallel rubric-based review across thirteen dimensions like problem framing, scope, metrics, and rollout. This analysis surfaces missing decisions and weak content, producing severity-tiered gaps and enhanced annotations for engineering handoff.

What is severity-based gap analysis for product requirement documents?

Severity-based gap analysis for product requirement documents converts review findings into graded P0, P1, and P2 gaps. This scoring mechanism gates delivery by prioritizing blocking issues over nice-to-improve items, ensuring teams focus on critical missing scope or compliance risks first.

Can I analyze a draft PRD from a URL or pasted text for compliance and rollout risks?

You can analyze a draft PRD supplied as pasted text, files, or URLs for compliance and rollout risks. The review evaluates legal, privacy, support impact, and cost dimensions, applying standard or lean workflows to identify gaps and generate machine-readable artifacts.

What's the best way to score and prioritize fixes for vague PRD scope?

The best way to prioritize fixes for vague PRD scope is using P0-gated scoring from a multi-dimension review. This approach converts inconsistent content into severity-tiered gaps, allowing you to address blocking issues before handing the enhanced document to engineering.

Does the PRD review process generate machine-readable artifacts for downstream workflows?

The PRD review process generates machine-readable review artifacts alongside an enhanced PRD version with suggested fixes. These outputs support downstream workflows by providing structured gap analysis and annotated documents after evaluating scenarios, approvals, risks, and cost.