prd-generator

Generate comprehensive PRDs with standardized templates and validation scripts.

194|26|Updated Oct 20, 2025

Search Tags:#planning #roadmap #prd #stakeholders #product-requirements

Ready to run

npx skills add https://github.com/jamesrochabrun/skills --skill prd-generator-jamesrochabrun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-generator
Source: https://github.com/jamesrochabrun/skills/tree/main/skills/prd-generator
Command: npx skills add https://github.com/jamesrochabrun/skills --skill prd-generator-jamesrochabrun

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ambiguous feature requests and scattered notes slow down product development. This Skill generates comprehensive PRDs to align stakeholders and steer delivery.

Core Features & Use Cases

PRD Structure: Executive summary, goals, user personas, stories, success metrics, scope.
User Stories: Clear acceptance criteria and scenarios.
Metrics & Scope: Success metrics and technical considerations.
Validation: PRD validation via templates and checklists.

Quick Start

Provide a feature brief (name, target users, problem) and ask for a PRD using the standard template in references/prd_template.md.

Frequently Asked Questions about prd-generator

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

FAQPage Schema

How do I create a comprehensive PRD from a feature idea?▼

A PRD (product requirements document) structures your feature idea into an actionable plan. Start with a brief describing the feature name, target users, and problem it solves, then use the standard PRD template to generate sections covering executive summary, goals, user personas, user stories, success metrics, scope, technical considerations, and risks. This aligns stakeholders and guides delivery.

What should a PRD include for product teams?▼

A complete PRD includes an executive summary, problem statement, goals, user personas, user stories with acceptance criteria, success metrics (KPIs), feature scope, technical considerations, design requirements, timeline, dependencies, risks, and open questions. This Skill generates each section using guided discovery prompts and validated templates to ensure nothing is missed.

How do I write user stories with clear acceptance criteria?▼

User stories capture what users need and why. This Skill generates stories in the format "As a [persona], I want [action], so that [benefit]" with specific acceptance criteria and scenarios. Reference examples guide the structure, ensuring stories are testable and actionable for development teams.

Can I validate my PRD against a standard template?▼

Yes. This Skill includes validation scripts and a reference PRD template that check your document for completeness across all key sections: goals, personas, stories, metrics, scope, and technical details. Validation ensures nothing critical is omitted before stakeholder review.

How do I define success metrics for a product feature?▼

Success metrics (KPIs) measure whether your feature achieves its goals. This Skill generates metrics tied to your user personas, goals, and business objectives—such as adoption rate, engagement time, or cost reduction—and structures them for tracking and reporting.

What format does the PRD export as?▼

The PRD exports as export-ready Markdown, making it easy to share, version in Git, convert to other formats, or embed in documentation systems. Markdown preserves structure and is readable both raw and rendered.