prp-prd

Generate structured PRDs from vague product ideas into markdown files.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/yandy-r/claude-plugins --skill prp-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prp-prd
Source: https://github.com/yandy-r/claude-plugins/tree/main/.cursor-plugin/skills/prp-prd
Command: npx skills add https://github.com/yandy-r/claude-plugins --skill prp-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams rapidly craft structured PRDs by guiding an interactive discovery process that turns vague ideas into concrete product specifications.

Core Features & Use Cases

  • Iterative PRD generation: guides users through Foundation → Market Grounding → Vision → Technical Feasibility → Decisions → Generate to produce a hypothesis-driven product spec.
  • Evidence-driven documentation: captures problems, market signals, user needs, constraints, and success metrics in a single PRD.
  • Decision-oriented collaboration: surfaces unresolved questions and decisions for cross-team alignment.

Quick Start

Describe your product idea and I will guide you through the PRD discovery process.

Frequently Asked Questions about prp-prd

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

FAQPage Schema
How do I generate a structured PRD from a vague product idea?

To generate a structured PRD from a vague product idea, describe your concept to initiate an interactive discovery process that iteratively builds a hypothesis-driven product specification. The skill guides you through defining problems, market grounding, technical feasibility, and decisions, saving the final output to docs/prps/prds/{name}.prd.md.

What sections should be included in a product requirements document for feature planning?

A comprehensive product requirements document for feature planning should include a problem statement, evidence, proposed solution, hypotheses, scope, success metrics, and a detailed technical approach. The skill automatically structures your PRD with these specific sections to ensure cross-team alignment.

Can I use an iterative process to turn rough feature requests into technical specifications?

Yes, you can use an iterative process to turn rough feature requests into technical specifications by progressing through structured phases: Foundation, Market Grounding, Vision, Technical Feasibility, and Decisions. This guided workflow captures user needs and constraints before final generation.

Does this PRD generator require any specific frameworks or dependencies to run?

No, this PRD generator does not require any specific frameworks or dependencies to run. It operates independently to guide the documentation process and outputs standard markdown files directly to your local docs/prps/prds/ directory.

How do I capture market signals and user needs for roadmap planning?

To capture market signals and user needs for roadmap planning, the skill applies an evidence-driven documentation approach during its Market Grounding phase. It systematically records market inputs and constraints directly into the final product spec for decision-making.

Why does my product spec need unresolved questions surfaced for cross-team alignment?

Your product spec needs unresolved questions surfaced for cross-team alignment because the PRD generation process is decision-oriented. Highlighting these open questions ensures that technical feasibility, scope, and proposed solutions are fully evaluated before development begins.