Mmcp.market

create-prd skill

by phuryn·phuryn/pm-skills·27k stars·MIT

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.

A100/100content scan

Is the create-prd skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the create-prd skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-execution/skills/create-prd ~/.claude/skills/create-prd
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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.
  1. 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?
  1. 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
  1. Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.
  1. Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.
  1. 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)

More skills from phuryn/pm-skills

  • Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
  • Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
  • Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
  • Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
  • Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
  • Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
  • Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
  • Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
  • Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
  • Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
  • Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
  • Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

All agent skills → · MCP servers