create-prd

Generate a structured PRD document with user stories and requirements.

69|11|Updated Dec 30, 2025

Search Tags:#planning #documentation #prd #product-management #user-stories #acceptance-criteria

Ready to run

npx skills add https://github.com/richtabor/agent-skills --skill create-prd-richtabor

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan features for a product by guiding you through clarifying questions and producing a complete PRD document ready for writing and execution.

Core Features & Use Cases

Interactive feature discovery: asks targeted questions to align stakeholders and capture requirements.
PRD generation: outputs a structured document with Introduction, Goals, User Stories, Functional/Non-Functional Requirements, Design Considerations, Technical Considerations, Success Metrics, and Open Questions.
Local save and reuse: saves PRD drafts under prds/[feature-name].md for versioning and collaboration.

Quick Start

Describe your feature request and follow the prompts to generate a detailed PRD.

Frequently Asked Questions about create-prd

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

FAQPage Schema

How do I create a PRD with user stories and acceptance criteria?▼

To create a PRD with user stories and acceptance criteria, describe your feature request and the tool interactively asks targeted questions to capture requirements, generating a structured document saved to prds/[feature-name].md.

What sections should be included in a product requirements document?▼

A product requirements document should include Introduction, Goals, User Stories, Functional Requirements, Non-Functional Requirements, Design Considerations, Technical Considerations, Success Metrics, and an Open Questions appendix.

Can I use interactive feature planning to align stakeholders before writing requirements?▼

Yes, interactive feature planning asks targeted clarifying questions to align stakeholders and capture requirements before generating the final product requirements document.

What is the best way to capture technical considerations and success metrics for a new feature?▼

The best way to capture technical considerations and success metrics is through guided interactive planning that systematically prompts for and documents these details within a structured PRD.

How do I save a PRD draft locally for versioning and collaboration?▼

To save a PRD draft locally for versioning and collaboration, the tool automatically writes the generated document to a markdown file at prds/[feature-name].md.

Do I need any specific tools or frameworks to plan product features?▼

No specific tools or frameworks are required to plan product features; you only need to provide a feature request description to start the interactive requirement gathering process.