# Create Prd

Create a lean, decision-ready Product Requirements Document with an 8-section template...

- Repository: https://github.com/phuryn/pm-skills (27597 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add phuryn/pm-skills --skill create-prd -g -a claude-code -y`
Codex: `npx skills add phuryn/pm-skills --skill create-prd -g -a codex -y`
Cursor: `npx skills add phuryn/pm-skills --skill create-prd -g -a cursor -y`
Gemini CLI: `npx skills add phuryn/pm-skills --skill create-prd -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add phuryn/pm-skills`

## Description

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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). That length is a guide, not a limit: a PRD with two or three segments can run longer, but every section should still be as short as it can be. 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. The value proposition follows the 6-part template in section 6.
- **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

The rest: https://github.com/phuryn/pm-skills/blob/HEAD/pm-execution/skills/create-prd/SKILL.md