Open Skills Logo
Open Skills

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 writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Author

@phuryn

Category

PM

Install

Hot:52

Download and extract to your skills directory

Copy command and send to OpenClaw for auto-install:

Download and install this skill https://openskills.cc/api/download?slug=phuryn-pm-execution-skills-create-prd&locale=en&source=copy
name:create-prddescription:"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 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

  • 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

    • Further Reading

  • How to Write a Product Requirements Document? The Best PRD Template.

  • A Proven AI PRD Template by Miqdad Jaffer (Product Lead @ OpenAI)