Create Prd
Draft a stakeholder-ready PRD with an 8-section template covering problem, objectives, segments, value props, solution, and release planning.
Overview
Create PRD is an agent skill most often used in Validate (also Build for ongoing PM) that produces a comprehensive 8-section Product Requirements Document from structured PM analysis.
Install
npx skills add https://github.com/phuryn/pm-skills --skill create-prdWhat is this skill?
- 8-section PRD template: Summary, Contacts, and six additional specification sections per skill instructions
- Step-by-step framing: problem, audience, success metrics, constraints before writing
- Supports ingesting user files and web research for market and customer context
- Oriented to align engineers, design, leadership, and stakeholders on one authoritative spec
Adoption & trust: 1.3k installs on skills.sh; 12.3k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know what you want to build loosely but lack an authoritative PRD that engineers and stakeholders can implement against.
Who is it for?
Indie founders and technical solos who need a formal feature or product spec before coding or hiring contractors.
Skip if: Teams that already have an approved spec and only need task breakdown, or pure engineering chores with no product ambiguity.
When should I use this skill?
Writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
What do I get? / Deliverables
You get a complete PRD draft aligned to the 8-section template, ready to hand off to design, implementation planning, or agent skills like writing-plans.
- 8-section Product Requirements Document
- Aligned problem, objectives, and release plan narrative
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate is the canonical shelf because a PRD locks scope and success criteria before full implementation commits engineering time. Scope subphase matches defining what to build, for whom, and how success is measured—the core job of a PRD.
Where it fits
Turn a validated problem into a full PRD before prototyping or hiring dev help.
Refresh requirements when scope shifts mid-build while keeping contacts and release sections current.
Structure early research notes into PRD sections once you have enough customer and market signal.
How it compares
Use instead of unstructured chat specs that omit contacts, release planning, and measurable objectives.
Common Questions / FAQ
Who is create-prd for?
Solo builders and small teams playing PM who must document product requirements clearly for engineers, designers, and leadership without a dedicated product org.
When should I use create-prd?
In Validate when scoping a feature or product; in Build under PM when refreshing specs mid-stream; after discovery when you are ready to write or audit a PRD or feature spec.
Is create-prd safe to install?
Review the Security Audits panel on this Prism page; do not upload confidential customer data or secrets when using web search for market context.
Workflow Chain
Then invoke: writing plans
SKILL.md
READMESKILL.md - Create 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 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 - [How to Write a Product Requirements Document? The Best PRD Template.](https://www.productcompass.pm/p/prd-template) - [A Proven AI PRD Template by Miqdad Jaffer (Product Lead @ OpenAI)](https://www.productcompass.pm/p/ai-prd-template)