create-prd

phuryn/pm-skills

Create comprehensive Product Requirements Documents with an 8-section template covering problem, objectives, segments, value propositions, and release planning.

Source View on skills.sh

What is create-prd?

This skill guides you through writing a complete Product Requirements Document (PRD) using a proven 8-section template. Use it when defining a new product, documenting feature requirements, preparing specifications, or reviewing existing PRDs to ensure alignment across engineering, design, and leadership.

Structures PRD creation with 8 key sections: Summary, Contacts, Background, Objective, Market Segments, Value Propositions, Solution, and Release planning
Helps analyze the problem, target audience, success metrics, and competitive advantages before writing
Guides detailed feature descriptions, UX/prototypes, technology considerations, and assumptions
Formats output as a markdown document saved with clear naming (PRD-[product-name].md)
Encourages data-driven, specific language accessible to non-technical stakeholders
Flags assumptions explicitly so teams can validate them

How to install create-prd

npx skills add https://github.com/phuryn/pm-skills --skill create-prd

Claude Code

Cursor

Windsurf

Cline

How to use create-prd

1.Gather information about your product or feature, including any existing documents, research, or customer data
2.Think through the core questions: What problem are we solving? Who are we solving it for? How will we measure success?
3.Follow the 8-section template in order: Summary, Contacts, Background, Objective, Market Segment(s), Value Proposition(s), Solution, and Release
4.Write each section using clear, accessible language avoiding jargon
5.Save the completed PRD as a markdown file named PRD-[product-name].md

Use cases

Good for

Writing a PRD for a new product feature or initiative from scratch
Documenting requirements for a feature specification to align engineering and design teams
Reviewing and improving an existing PRD to ensure all critical sections are covered
Preparing product strategy documentation for leadership and stakeholder alignment
Creating market segment and value proposition analysis for competitive positioning

Who it's for

Product managers defining new features or products
Product leads preparing specifications for development teams
Startup founders documenting product vision and requirements
Teams aligning on product strategy and success metrics
Anyone responsible for translating business goals into product specifications

create-prd FAQ

What if I don't have all the information for every section?

Start with what you know and flag assumptions clearly. The PRD template helps identify gaps in your thinking that the team can research and validate together.

Should I include exact dates in the Release section?

No. Use relative timeframes (e.g., 'first 2 weeks', 'next quarter') instead of specific dates, as product timelines often shift.

How detailed should the Solution section be?

Include enough detail for engineers and designers to understand the approach: wireframes/user flows, key feature descriptions, relevant technology notes, and any unproven assumptions.

What is the Value Curve framework mentioned in the template?

The Value Curve is a strategic analysis tool that compares your product's strengths and weaknesses against competitors across key attributes, helping identify competitive advantages.

Who should be listed in the Contacts section?

Include key stakeholders with decision-making authority or critical input: product owner, engineering lead, design lead, and any other roles essential to the initiative.

Full instructions (SKILL.md)

Source of truth, from phuryn/pm-skills.

name: create-prd description: "Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD."

Create a Product Requirements Document

Purpose

You are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.

Context

A well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-section template proven to communicate product vision effectively to engineers, designers, leadership, and stakeholders.

Instructions

Gather Information: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.
Think Step by Step: Before writing, analyze:
- What problem are we solving?
- Who are we solving it for?
- How will we measure success?
- What are our constraints and assumptions?
Apply the PRD Template: Create a document with these 8 sections:

1. Summary (2-3 sentences)
- What is this document about?
2. Contacts
- Name, role, and comment for key stakeholders
3. Background
- Context: What is this initiative about?
- Why now? Has something changed?
- Is this something that just recently became possible?
4. Objective
- What's the objective? Why does it matter?
- How will it benefit the company and customers?
- How does it align with vision and strategy?
- Key Results: How will you measure success? (Use SMART OKR format)
5. Market Segment(s)
- For whom are we building this?
- What constraints exist?
- Note: Markets are defined by people's problems/jobs, not demographics
6. Value Proposition(s)
- What customer jobs/needs are we addressing?
- What will customers gain?
- Which pains will they avoid?
- Which problems do we solve better than competitors?
- Consider the Value Curve framework
7. Solution
- 7.1 UX/Prototypes (wireframes, user flows)
- 7.2 Key Features (detailed feature descriptions)
- 7.3 Technology (optional, only if relevant)
- 7.4 Assumptions (what we believe but haven't proven)
8. Release
- How long could it take?
- What goes in the first version vs. future versions?
- Avoid exact dates; use relative timeframes
Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.
Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.
Save the Output: If the PRD is substantial (which it will be), save it as a markdown document in the format: PRD-[product-name].md