prd-generator

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.

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.

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.

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.

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.

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.