create-prd · git:20261009.55c8ec0 · 2026-10-09 · sha256 a5ad42f818abcc72

create-prd git:20261009.55c8ec0A

Immutable. This exact content never changes and is served at /api/v1/blob/a5ad42f818abcc72.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_rngygtyc5dhgoy5k/a5ad42f818abcc72093d99a7a5f2800af79169cd486777af31c163bb83ef501d.json

Then /plugin install create-prd@markdownregistry-rngygtyc5dhgoy5k in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: create-prd
description: "Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions, solution, and release. Lean by default (about one to two pages), with a fuller spec on request. 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 writing a PRD for the product or feature the user describes. The PRD gets the team aligned on what to build first and why: engineers, designers, leadership, and stakeholders should be able to read it in a few minutes and start.

## Lean by default

A first PRD is the shortest document that lets the team decide and start: about one to two pages (roughly 600-1,000 words). Write a longer, more detailed version only when the user asks for one.

- **Complete means no gap that blocks a decision about the first version**, not every question answered. The questions under each section below are a checklist to pick from: answer the ones that matter for this initiative and skip the rest.
- **A section with little to say gets a line or two.** If you don't know the contacts, leave the Contacts section out entirely; don't list roles to fill in later. Never pad a section or fill it with "TBD".
- **Market Segments and Value Propositions are always included.** They are the core of this template: who has the problem, and why they would care.
- **Don't invent.** What you don't know goes to 7.4 Assumptions and open questions, clearly marked, not into the body as fact.

## Instructions

1. **Start from what the user gave you.** Read any files they provide. If the problem, the target users, or how success will be measured is missing, stop and ask about them first: up to three short questions in one message, and no PRD in that reply. Write the PRD after the answers. Write it without them only if the user tells you to go ahead, and then mark those gaps as assumptions. Use web search only when the user points to sources or asks for market context, not to pad the document.

2. **Think before writing** (this stays out of the document): what problem are we solving, for whom, how will we know it worked, and what is the smallest first version that tests it?

3. **Write the 8 sections.** The lean version answers only what matters; the detailed version goes through more of the questions.

   **1. Summary** (2-3 sentences)
   - What is this, for whom, and why now?

   **2. Contacts** (optional in the lean version)
   - Name, role, and comment for key stakeholders

   **3. Background**
   - Context: what is this initiative about?
   - Why now? Has something changed, or just become possible?

   **4. Objective**
   - What's the objective, and why does it matter to customers and the company?
   - How does it align with the vision and strategy? (one line, if relevant)
   - Key Results: 1-3 measurable results (SMART OKR format)

   **5. Market Segment(s)** (always included)
   - For whom are we building this? Define segments by people's problems or jobs, not demographics.
   - What constraints exist?

   **6. Value Proposition(s)** (always included)
   - What customer jobs or needs are we addressing?
   - What will customers gain, and which pains will they avoid?
   - Which problems do we solve better than the alternatives? (the Value Curve framework belongs in the detailed version)

   **7. Solution**
   - 7.1 UX/Prototypes: the key flow, or a link to wireframes (skip if there are none yet)
   - 7.2 Key Features: the must-haves for the first version, a line or two each
   - 7.3 Technology (optional, only if relevant)
   - 7.4 Assumptions and open questions: what we believe but haven't proven, and what we still need to find out

   **8. Release**
   - What goes in the first version, what comes later, and what we are explicitly not doing
   - How long could it take? Use relative timeframes, not exact dates.

4. **Use accessible language.** Write for a primary school graduate. Avoid jargon. Use clear, short sentences.

5. **Save the output** as a markdown document: `PRD-[product-name].md`.

6. **Say what you left out.** In your reply, not in the document, add one short line listing what you skipped on purpose (for example: competitive analysis, detailed UX flows, rollout plan), so the user can ask you to expand any section.

## Reviewing an existing PRD

Check it against the same standard: Is anything missing that blocks a decision about the first version? Are Market Segments and Value Propositions there, and specific? Are assumptions marked as assumptions? What could be cut without losing anything the team needs? Return the gaps first, then the cuts.

## Notes

- Lean is the default; detail is on request.
- Be specific and data-driven where possible: a number or a named user group beats an adjective.
- Flag assumptions clearly so the team can validate them.
- Non-goals matter as much as goals: say what the first version will not do.

---

### 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)