prd-quality-review

Review PRD drafts for ambiguity, contradictions, and readiness before engineering handoff.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill prd-quality-review-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-quality-review
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/prd-quality-review
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill prd-quality-review-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? PRDs often reach engineering with vague requirements, hidden contradictions, missing scope decisions, and untestable acceptance logic, causing rework and delivery confusion. This Skill performs a structured final quality review of an existing PRD draft from the perspectives of product, design, engineering, QA, and operations. ## Core Features & Use Cases - Multi-dimensional review: Checks problem clarity, target users, release scope, workflows, functional and non-functional requirements, metrics, dependencies, risks, and cross-section consistency. - Failure-mode detection: Identifies common PRD problems such as untestable requirements, duplicated or conflicting requirements, vague metrics, and unresolved decisions hidden inside requirements. - Structured Russian-language report: Produces a verdict (strong / workable / weak), key ambiguities with recommended clarifications, missing decisions, prioritized edits, and a final readiness checklist. - Use Case: Before handing a PRD to engineering, paste the draft and ask for a final red-team review to surface the points where the team would still need to guess. ## Quick Start Use the prd-quality-review skill to red-team this PRD draft and tell me whether it is ready for engineering handoff.

Frequently Asked Questions about prd-quality-review

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

FAQPage Schema
How do I review a PRD before engineering handoff?

Read the PRD end to end and check release scope, target users, workflows, requirement testability, metrics, dependencies, and risks. This Skill automates that review and outputs a structured verdict with prioritized edits and a readiness checklist.

What are common PRD mistakes that cause delivery problems?

Common failure modes include unclear primary users, overly broad scope, missing out-of-scope sections, untestable requirements, vague metrics, unnamed dependencies, duplicated or conflicting requirements, and unresolved decisions hidden inside requirements.

How do I check if PRD requirements are testable?

A requirement is testable when QA can verify it objectively without interpretation. The review flags requirements with vague wording, missing acceptance logic, or ambiguous edge cases and recommends concrete clarifications for each.

When should I not use a final PRD quality review?

Do not use it when no PRD draft exists yet, since the Skill reviews existing documents rather than writing them. It is also not suited for early ideation or strategy definition, only for pre-handoff validation.

What output does a PRD quality review produce?

The review produces a Russian-language report with an overall quality verdict, strengths, key ambiguities with recommended clarifications, contradictions, missing decisions, delivery confusion points, prioritized edits, and a final readiness checklist.