What Content Does the create-prd Skill Cover?
The create-prd skill generates a comprehensive eight-section Product Requirements Document (PRD) template that guides product teams from initial concept through release planning, covering objectives, market segments, solution details, and risk management.
The create-prd skill in the phuryn/pm-skills repository provides product managers with a standardized framework for documenting product requirements. According to the source code in pm-execution/skills/create-prd/SKILL.md, this execution skill eliminates manual formatting by producing a structured markdown template through the write-prd command, ensuring consistency across product teams while still allowing customization.
Eight-Section PRD Framework
The skill produces a complete document structure divided into eight distinct sections. Each section serves a specific purpose in the product lifecycle:
1. Summary
A concise one-paragraph overview capturing the product’s purpose and the core problem it solves. This section provides stakeholders with immediate context without requiring deep technical knowledge.
2. Background
Contextual information about market conditions, user research findings, and prior discoveries that motivate the product effort. This grounds the document in real data rather than assumptions.
3. Objectives
Clear, measurable goals including KPIs and success metrics that define when the product achieves its intended outcomes. These metrics align engineering and business teams on deliverables.
4. Market Segments
Identification of target user personas or market slices, including sizing and priority rankings. This ensures the solution addresses the right audience with appropriate resource allocation.
5. Value Propositions
The unique benefits delivered to each identified segment, explicitly aligned with the objectives. This section differentiates the product from existing alternatives.
6. Solution Details
High-level descriptions of product features, architectural decisions, and technical constraints. This bridges the gap between business requirements and implementation planning.
7. Release Planning
Timelines, milestones, dependencies, and rollout strategies such as MVP launches followed by phased releases. This creates accountability for delivery schedules.
8. Risks & Assumptions
Key risks, underlying assumptions, and mitigation plans requiring tracking throughout development. This proactive approach prevents surprises during execution.
How to Use the create-prd Skill
The skill is invoked via the write-prd command documented in pm-execution/commands/write-prd.md. Below are practical implementation patterns:
Generate a fresh PRD template:
pm write-prd --skill create-prd
This creates a markdown file PRD.md pre-populated with the eight sections listed above.
Inject external research data automatically:
pm write-prd --skill create-prd --input interview_summary.txt
The skill inserts interview findings into the Background and Value Propositions sections based on content analysis.
Convert to PDF for stakeholder distribution:
pm write-prd --skill create-prd | pandoc -f markdown -t pdf -o PRD.pdf
Source Files and Implementation
The create-prd skill implementation spans several key files within the repository:
pm-execution/skills/create-prd/SKILL.md— Contains the full skill definition, including metadata, section headings, and prompt templates that structure the output.pm-execution/commands/write-prd.md— Documents thewrite-prdcommand interface, including available flags like--skilland--input.README.md— Provides a top-level overview of all execution skills, including a brief description ofcreate-prdcapabilities.pm-execution/README.md— Offers a detailed execution-skill reference specifically listing the eight-section PRD template structure.
Summary
- The
create-prdskill produces an eight-section PRD template covering Summary, Background, Objectives, Market Segments, Value Propositions, Solution Details, Release Planning, and Risks & Assumptions. - Execution occurs through the
write-prdcommand with the--skill create-prdflag. - The skill definition resides in
pm-execution/skills/create-prd/SKILL.md. - External input files can be automatically mapped to specific sections using the
--inputparameter. - Output format is standard markdown, enabling further processing with tools like Pandoc for PDF generation.
Frequently Asked Questions
What command triggers the create-prd skill?
The skill is triggered using pm write-prd --skill create-prd, as implemented in the command handler documented at pm-execution/commands/write-prd.md. This command invokes the template engine defined in the skill’s metadata file.
Which repository file contains the complete skill definition?
The complete definition, including section prompts and metadata, is stored in pm-execution/skills/create-prd/SKILL.md. This file specifies the eight-section structure and how the write-prd command should render each component.
Can the create-prd skill integrate external interview data?
Yes. By appending --input interview_summary.txt to the command, the skill automatically inserts external findings into the Background and Value Propositions sections, streamlining the documentation of user research.
How many sections does the generated PRD template include?
The template generates exactly eight sections: Summary, Background, Objectives, Market Segments, Value Propositions, Solution Details, Release Planning, and Risks & Assumptions. This structure is standardized across all invocations of the skill.
Have a question about this repo?
These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →