review-prd

Review PRDs for structural completeness, quality, and anti-patterns.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill review-prd-jerelvelarde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-prd
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/review-prd
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill review-prd-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically evaluate PRDs for clarity, alignment with user needs, and potential anti-patterns, preventing missed requirements and design flaws.

Core Features & Use Cases

  • Structured evaluation of PRDs against a comprehensive checklist covering problem clarity, user focus, success metrics, scope, risks, dependencies, and feasibility.
  • Actionable reporting that documents findings, recommended fixes, and a final verdict to guide product and engineering decisions.
  • Applicable to internal product specs, partner PRDs, and early-stage concept documents to ensure consistent quality across documents.

Quick Start

Provide the PRD path or name to begin the review.

Frequently Asked Questions about review-prd

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

FAQPage Schema
How do I review a PRD for structural completeness and quality?

Reviewing a PRD for structural completeness involves checking the document against a checklist covering problem clarity, user focus, success metrics, scope, risks, and feasibility. This process maps each checklist item to findings and actionable fixes.

What is the best way to evaluate a product requirements document for anti-patterns?

Evaluating a product requirements document for anti-patterns requires cross-checking the specifications against JTBD, user personas, and the existing architecture. This identifies design flaws and missed requirements within the document.

How do you assess if a PRD is ready for engineering?

Assessing if a PRD is ready for engineering involves producing a structured assessment that maps findings to actionable fixes. This results in a final verdict of Ready for Engineering, Needs Revisions, or Needs Rewrite.

Can I use a PRD checklist for early-stage product concept documents?

Yes, a PRD checklist can be applied to early-stage concept documents, internal product specs, and partner PRDs. This ensures consistent quality and alignment with user needs across all product documentation.

What should a product requirements document review cover to prevent missed requirements?

A product requirements document review should cover problem clarity, user focus, success metrics, scope, risks, dependencies, and feasibility within existing architecture. This prevents missed requirements and design flaws.

When do I need a structured assessment for my product spec?

You need a structured assessment for your product spec when you want to systematically evaluate clarity, align with user needs, and identify potential anti-patterns before handing the document over to engineering.