prd-crit

Analyze product requirement drafts for claim validity, section completeness, and content consistency.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/aminianp/skills --skill prd-crit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-crit
Source: https://github.com/aminianp/skills/tree/main/skills/prd-crit
Command: npx skills add https://github.com/aminianp/skills --skill prd-crit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables systematic review and critique of PRD drafts, sections, or notes, helping teams identify gaps, inconsistencies, and claims requiring evidence for clearer, more reliable product specifications.

Core Features & Use Cases

  • Claims Classification: Identifies and classifies major claims and assumptions within PRDs as data-backed, anecdotal, or hypotheses.
  • Content Feedback: Provides specific feedback on clarity, vagueness, and formatting issues directly related to product documentation.
  • Coverage Analysis: Flags missing elements such as JTBDs, user journeys, success metrics, and non-goals, ensuring comprehensive PRDs.
  • Use Case: Analyze a product spec to ensure all claims are supported, key sections are complete, and relationships between objectives and metrics are consistent before stakeholder review.

Quick Start

Load a product requirements document into your preferred Markdown or text editor and invoke this Skill to analyze its claims, coverage, and coherence, ensuring a complete and validated PRD.

Frequently Asked Questions about prd-crit

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

FAQPage Schema
How do I review a product requirement document for missing sections and inconsistencies?

Analyzing a PRD for missing sections involves checking coverage of JTBDs, user journeys, success metrics, and non-goals. This Skill flags missing elements and evaluates relationships between objectives and metrics to ensure comprehensive PRDs.

What is claim classification in product requirements and how does it work?

Claim classification in product requirements identifies and categorizes major claims and assumptions as data-backed, anecdotal, or hypotheses. This mechanism ensures that every assertion within a PRD is evaluated for evidence support before stakeholder review.

How to validate PRD claims and assumptions before stakeholder review?

Validating PRD claims requires classifying assertions as data-backed, anecdotal, or hypotheses, then verifying evidence support. This Skill analyzes product specs to ensure all claims are supported and key sections are complete prior to stakeholder review.

Can I use a text editor to analyze product specs for coverage and coherence?

Yes, you can load a product requirements document into a preferred Markdown or text editor and invoke this Skill to analyze its claims, coverage, and coherence, ensuring a complete and validated PRD without needing external dependencies.

What is the best way to identify gaps and vague formatting in PRDs?

Identifying gaps and vague formatting in PRDs requires structured content feedback on clarity and formatting issues. This Skill provides specific critique directly related to product documentation, highlighting inconsistencies and areas requiring evidence.