Create Prd
- 2.3k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
create-prd is an agent skill that Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, .
About
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 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 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 2 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 3 Apply the PRD Template Create a document with these 8 sections
- description: "Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectiv
- You are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for
- A well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-secti
- Follow create-prd SKILL.md steps and documented constraints.
- Follow create-prd SKILL.md steps and documented constraints.
Create Prd by the numbers
- 2,317 all-time installs (skills.sh)
- +96 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #446 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
create-prd capabilities & compatibility
- Capabilities
- description: "create a product requirements docu · you are an experienced product manager responsib · a well structured prd clearly communicates the w · follow create prd skill.md steps and documented
- Use cases
- orchestration
What create-prd says it does
description: "Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writi
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
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, desig
npx skills add https://github.com/phuryn/pm-skills --skill create-prdAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.3k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
When should an agent use create-prd and what problem does it solve?
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, docu
Who is it for?
Developers invoking create-prd as documented in the skill source.
Skip if: Skip when requirements fall outside create-prd documented scope.
When should I use this skill?
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, docu
What you get
Outputs aligned with the create-prd SKILL.md workflow and stated deliverables.
- 8-section Product Requirements Document
By the numbers
- Uses an 8-section PRD template
Files
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
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.
2. 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?
3. 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
4. Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.
5. Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.
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
Notes
- Be specific and data-driven where possible
- Link each section back to the overall strategy
- Flag assumptions clearly so the team can validate them
- Keep the document concise but complete
---
Further Reading
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Choose create-prd over ad-hoc feature notes when you need a full stakeholder-facing specification with problem, segments, and release planning in one structured document.
FAQ
What is create-prd?
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when
When should I use create-prd?
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when
Is create-prd safe to install?
Review the Security Audits panel on this page before production use.