A living specification that defines the problem, objectives, segments, value propositions, solution, and release plan to guide product teams.

How long does PRD creation take?

It varies by scope; small features may take a few hours while larger initiatives can take days to a week or more.

Can this PRD template be reused for future features?

Yes. The eight section structure provides a reusable framework that you can copy and tailor for new work, updating assumptions and success metrics as you proceed.

create-prd

Scanned

npx machina-cli add skill phuryn/pm-skills/create-prd --openclaw

Files (1)

SKILL.md

3.5 KB

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

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

Source

git clone https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/create-prd/SKILL.mdView on GitHub

Overview

This skill helps you craft a comprehensive Product Requirements Document (PRD) using an eight section template. It clarifies the problem, objectives, market segments, value propositions, solution details, and release planning to align stakeholders and guide development. Output is a clear markdown PRD ready for sharing and review.

How This Skill Works

First gather inputs such as problem, users, constraints and success metrics. Then structure the document into eight sections (Summary, Contacts, Background, Objective, Market Segment(s), Value Proposition(s), Solution, Release) and fill each with concise, data driven content. Finally save the artifact as PRD-[product-name].md for distribution.

When to Use It

Starting a new feature or product initiative and need a single source of truth.
Documenting product requirements for engineers, designers, and QA.
Reviewing or updating an existing PRD to reflect changed constraints or learnings.
Aligning multiple stakeholders on scope, success metrics, and release plan.
Planning releases and defining SMART OKRs to measure outcomes.

Quick Start

Step 1: Gather problem, users, constraints, and success metrics.
Step 2: Fill the 8-section PRD template (Summary through Release) with concise, data driven content.
Step 3: Review with stakeholders and save as PRD-[product-name].md.

Best Practices

Anchor the PRD with a clear problem statement and measurable objectives.
Define market segments by jobs to be done, not demographics.
Use the eight-section structure and flag assumptions with evidence.
Include UX prototypes or flows where possible to reduce ambiguity.
Inspect and revise with stakeholders; keep language simple and concrete.

Example Use Cases

SaaS onboarding feature PRD outlining success metrics.
Mobile app offline mode PRD with release milestones.
B2B API integration PRD focusing on data contracts and performance.
Marketplace listing flow PRD detailing evaluation, steps, and KPIs.
Customer support chatbot PRD with intent coverage and guardrails.

Frequently Asked Questions

Add this skill to your agents