create-prd

Name: create-prd
Author: phuryn

2.1kinstalls2.5kforks

How to install create-prd?

phuryn/pm-skills/create-prd

$npx -y skills add phuryn/pm-skills --skill create-prd

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Create a Product Requirements Document
2
3	## Purpose
4
5	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.
6
7	## Context
8
9	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.
10
11	## Instructions
12
13	1. 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.
14
15	2. Think Step by Step: Before writing, analyze:
16	- What problem are we solving?
17	- Who are we solving it for?
18	- How will we measure success?
19	- What are our constraints and assumptions?
20
21	3. Apply the PRD Template: Create a document with these 8 sections:
22
23	1. Summary (2-3 sentences)
24	- What is this document about?
25
26	2. Contacts
27	- Name, role, and comment for key stakeholders
28
29	3. Background
30	- Context: What is this initiative about?
31	- Why now? Has something changed?
32	- Is this something that just recently became possible?
33
34	4. Objective
35	- What's the objective? Why does it matter?
36	- How will it benefit the company and customers?
37	- How does it align with vision and strategy?
38	- Key Results: How will you measure success? (Use SMART OKR format)
39
40	5. Market Segment(s)
41	- For whom are we building this?
42	- What constraints exist?
43	- Note: Markets are defined by people's problems/jobs, not demographics
44
45	6. Value Proposition(s)
46	- What customer jobs/needs are we addressing?
47	- What will customers gain?
48	- Which pains will they avoid?
49	- Which problems do we solve better than competitors?
50	- Consider the Value Curve framework
51
52	7. Solution
53	- 7.1 UX/Prototypes (wireframes, user flows)
54	- 7.2 Key Features (detailed feature descriptions)
55	- 7.3 Technology (optional, only if relevant)
56	- 7.4 Assumptions (what we believe but haven't proven)
57
58	8. Release
59	- How long could it take?
60	- What goes in the first version vs. future versions?
61	- Avoid exact dates; use relative timeframes
62
63	4. Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.
64
65	5. Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.
66
67	6. 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`
68
69	## Notes
70
71	- Be specific and data-driven where possible
72	- Link each section back to the overall strategy
73	- Flag assumptions clearly so the team can validate them
74	- Keep the document concise but complete
75
76	---
77
78	### Further Reading
79
80	- [How to Write a Product Requirements Document? The Best PRD Template.](https://www.productcompass.pm/p/prd-template)
81	- [A Proven AI PRD Template by Miqdad Jaffer (Product Lead @ OpenAI)](https://www.productcompass.pm/p/ai-prd-template)

People who liked this also viewed

6 picks

Type

create-prd

2.1kinstalls2.5kforks

View on GitHub

How to install create-prd?

phuryn/pm-skills/create-prd

$npx -y skills add phuryn/pm-skills --skill create-prd

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Create a Product Requirements Document
2
3	## Purpose
4
5	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.
6
7	## Context
8
9	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.
10
11	## Instructions
12
13	1. 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.
14
15	2. Think Step by Step: Before writing, analyze:
16	- What problem are we solving?
17	- Who are we solving it for?
18	- How will we measure success?
19	- What are our constraints and assumptions?
20
21	3. Apply the PRD Template: Create a document with these 8 sections:
22
23	1. Summary (2-3 sentences)
24	- What is this document about?
25
26	2. Contacts
27	- Name, role, and comment for key stakeholders
28
29	3. Background
30	- Context: What is this initiative about?
31	- Why now? Has something changed?
32	- Is this something that just recently became possible?
33
34	4. Objective
35	- What's the objective? Why does it matter?
36	- How will it benefit the company and customers?
37	- How does it align with vision and strategy?
38	- Key Results: How will you measure success? (Use SMART OKR format)
39
40	5. Market Segment(s)
41	- For whom are we building this?
42	- What constraints exist?
43	- Note: Markets are defined by people's problems/jobs, not demographics
44
45	6. Value Proposition(s)
46	- What customer jobs/needs are we addressing?
47	- What will customers gain?
48	- Which pains will they avoid?
49	- Which problems do we solve better than competitors?
50	- Consider the Value Curve framework
51
52	7. Solution
53	- 7.1 UX/Prototypes (wireframes, user flows)
54	- 7.2 Key Features (detailed feature descriptions)
55	- 7.3 Technology (optional, only if relevant)
56	- 7.4 Assumptions (what we believe but haven't proven)
57
58	8. Release
59	- How long could it take?
60	- What goes in the first version vs. future versions?
61	- Avoid exact dates; use relative timeframes
62
63	4. Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.
64
65	5. Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.
66
67	6. 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`
68
69	## Notes
70
71	- Be specific and data-driven where possible
72	- Link each section back to the overall strategy
73	- Flag assumptions clearly so the team can validate them
74	- Keep the document concise but complete
75
76	---
77
78	### Further Reading
79
80	- [How to Write a Product Requirements Document? The Best PRD Template.](https://www.productcompass.pm/p/prd-template)
81	- [A Proven AI PRD Template by Miqdad Jaffer (Product Lead @ OpenAI)](https://www.productcompass.pm/p/ai-prd-template)

People who liked this also viewed

6 picks

Type