skills.rest
ximing
ximingCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review-prd

Analyze requirement documents for clarity, ambiguity, and completeness.

Updated Mar 16, 2026
Search Tags:#requirements#clarity#ambiguity#technical design#prd#specification review
One-click install
npx skills add https://github.com/ximing/spark --skill review-prd-ximing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-prd
Source: https://github.com/ximing/spark/tree/main/.claude/skills/review.prd
Command: npx skills add https://github.com/ximing/spark --skill review-prd-ximing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill identifies ambiguities, inconsistencies, and missing information in requirement documents (PRDs, specifications, business rules) that would hinder the creation of clear and feasible technical solutions.

Core Features & Use Cases

  • Clarity Assessment: Analyzes requirements for clarity, completeness, and lack of ambiguity.
  • Problem Identification: Pinpoints specific issues like undefined terms, conflicting rules, unclear processes, and missing non-functional requirements.
  • Actionable Feedback: Provides structured reports with prioritized blocking issues, suggestions for rewriting, and a minimal set of information needed for technical design.
  • Use Case: Submit a draft PRD to the skill and receive a report detailing all areas that need clarification before engineering can begin, ensuring a smoother development process.

Quick Start

Use the review-prd skill to check if the provided requirement document is clear enough to start technical design.

Frequently Asked Questions about review-prd

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

FAQPage Schema
How do I check if my PRD is ready for technical design?▼

To check if a PRD is ready for technical design, analyze the requirement document for clarity, ambiguity, and completeness to identify undefined terms, conflicting rules, and missing non-functional requirements that block architecture and development.

What specific ambiguities should I look for in specification review?▼

Specification review targets ambiguities that impede engineering, including undefined terms, conflicting business rules, unclear processes, and missing non-functional requirements necessary for architecture, integration, acceptance, and scheduling.

How do I identify blocking issues in a requirements document?▼

Identify blocking issues in a requirements document by analyzing its completeness and pinpointing specific missing definitions and information gaps that hinder the creation of clear, feasible technical solutions.

Can I get actionable rewrite suggestions for unclear business rules?▼

Yes, you can receive actionable feedback for unclear business rules through structured reports that provide prioritized blocking issues, rewrite suggestions, and a minimal set of information needed for technical design.

When do I need to perform a clarity assessment on my requirements?▼

Perform a clarity assessment on requirements when you have a draft PRD and need to ensure all areas are clarified before engineering begins, ensuring a smoother development process and accurate scheduling.

Related Skills

Explore More Product & Management Skills→
agol586agol586

speckit-checklist

Validate technical requirements for ambiguities, missing edge cases, and non-functional gaps.

Community
Intermediate
EONMUNEONMUN
1

spec_driven_development.plan

Convert clarified specifications into technical plans with architecture, data models, and API contracts.

Official
Advanced
CodenburgCodenburg

sdd-design

Generate technical design documents from proposals and specifications.

Community
Advanced
TravisLeeeeeeTravisLeeeeee
110

Proofreader

Proofreads grammar, spelling, punctuation, syntax, style consistency, and readability in documents.

Community
Intermediate