skills.rest
gabriellst
gabriellstCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prd

Generate a structured PRD.md document from product ideas or feature descriptions.

4|Updated Jul 30, 2026
Search Tags:#personas#user flows#prd#product requirements#generate#scope definition#success metrics
One-click install
npx skills add https://github.com/gabriellst/codm --skill prd-gabriellst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/gabriellst/codm/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/gabriellst/codm --skill prd-gabriellst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often build features based on assumptions instead of explicit decisions. This Skill turns a raw product idea, feature description, or stakeholder conversation into a complete PRD.md with structured requirements, personas, user flows, and measurable success metrics. ## Core Features & Use Cases - Structured Requirements: Produces functional requirements with priorities (Must/Should/Nice to Have) and acceptance criteria, plus non-functional requirements covering performance, security, and accessibility. - Scope & Risk Definition: Explicitly documents in-scope and out-of-scope items, risks with mitigations, open questions, and assumptions. - Use Case: A stakeholder describes a clinic dashboard idea in a meeting. Use this Skill to ask clarifying questions, then generate a PRD.md with personas, user flows, and success metrics that downstream user stories and tech specs can reference. ## Quick Start Ask the AI to generate a PRD.md from your product idea or feature description, answering its clarifying questions about users, scope, and constraints.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a PRD from a product idea?▼

Provide the product idea or feature description and answer clarifying questions about users, problem, and constraints. The Skill generates a PRD.md with vision, personas, functional requirements, user flows, scope, risks, and success metrics.

What sections should a product requirements document include?▼

This PRD template includes overview, vision, user personas, functional requirements with priorities and acceptance criteria, non-functional requirements, user flows, scope boundaries, risks, open questions, and documented assumptions.

When should I not generate a new PRD?▼

Skip generation when a PRD.md already exists and only needs small updates, when breaking existing requirements into user stories, or when making architectural decisions. Edit the existing document directly in those cases.

How are functional requirements prioritized in a PRD?▼

Each requirement is labeled Must Have, Should Have, or Nice to Have. Must Have means the product is not viable without it, Should Have is important but not launch-blocking, and Nice to Have can be deferred.

Can a PRD include implementation or architecture details?▼

No. The Skill explicitly keeps implementation details out of requirements, focusing on problem statements, user needs, and measurable outcomes. Architectural decisions belong in a separate tech spec step.

Related Skills

Explore More Product & Management Skills→
MushroomFleetMushroomFleet
2

Twenty_Questions

Conduct adaptive twenty-question interviews and update a markdown artifact.

Community
Intermediate
tojooliviertojoolivier

requirements-spec-writer

Create structured requirements documents, user stories, and technical specifications.

Community
Advanced
orqesaorqesa

product_marketing

Analyze buyer personas, market trends, and competitor activities for go-to-market strategies.

Official
Advanced
striderZAstriderZA
72

explore

Run time-boxed prototypes to validate game concepts with verdict reports.

Community
Intermediate