Skip to main content
command CX Codex

write-prd — Claude Code command: what it does, how to install

write-prd generates a lean Product Requirements Document from a brief idea, customer request, or uploaded problem summary.

MIT ★ 28,211 updated 2026-10-16

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add phuryn/pm-skills
/plugin install pm-execution@pm-skills
Open on GitHub

What write-prd does

The command takes a feature name, user complaint, or pasted research document and drafts a lean one-to-two-page PRD. If core context is missing, it asks at most three targeted questions in a single reply: the user problem, target audience, and measurable success criteria. Tell it to draft right away, and it treats missing points as explicit assumptions.

The generated document follows an 8-section layout: Summary, Contacts, Background, Objective, Market Segments, Value Propositions, Solution, and Release. Value propositions follow a 6-part structure, while out-of-scope items go straight into the Release section. The resulting draft is saved directly to your workspace as a Markdown file.

Execution depends on the create-prd skill, so make sure the underlying execution plugin is installed.

What it helps with

  • turn a vague feature idea into a lean product requirements spec
  • clarify target user segments and alternative workarounds
  • define measurable outcome metrics before engineering starts
  • write out-of-scope boundaries to prevent early feature bloat

Example prompts for the agent

  • /write-prd SSO support for enterprise customers
  • /write-prd Users are dropping off during onboarding — we need to fix step 3
  • /write-prd export workspace data to CSV

How to install write-prd

1Plugin marketplace

/plugin marketplace add phuryn/pm-skills
/plugin install pm-execution@pm-skills

2Manually: put the files in place

.claude/commands/write-prd.md

Call it with /write-prd. For all projects use ~/.claude/commands/

Questions about write-prd

How to install write-prd in Claude Code?

Run /plugin marketplace add phuryn/pm-skills in Claude Code, then run /plugin install pm-execution@pm-skills. Alternatively, add .claude/commands/write-prd.md to your project.

What does the write-prd command do?

It structures incoming notes, problems, or briefs into an 8-part PRD saved to a Markdown file. By default it creates a short two-page draft, keeping detailed specs optional.

Can it run without answering follow-up questions?

Yes. If you tell Claude Code to write immediately, it skips questions and documents the missing context as explicit assumptions in the Solution section.

Source text

write-prd.md · MIT
---
description: Create a lean Product Requirements Document from a feature idea or problem statement, with a fuller spec on request
argument-hint: "<feature or problem statement>"
---

# /write-prd -- Product Requirements Document

Create a lean PRD that aligns stakeholders and guides development. Accepts anything from a vague idea to a detailed brief.

## Invocation

```
/write-prd SSO support for enterprise customers
/write-prd Users are dropping off during onboarding — we need to fix step 3
/write-prd [upload a brief, research doc, or strategy deck]
```

## Workflow

### Step 1: Understand the Feature

Accept the input in any form:
- A feature name ("SSO support")
- A problem statement ("Enterprise customers keep asking for centralized auth")
- A user request ("Users want to export their data as CSV")
- A vague idea ("We should do something about onboarding drop-off")
- An uploaded document (brief, research, Slack thread, email)

### Step 2: Fill Only the Gaps That Matter

Extract what the input already gives you, and research what the web can answer (prior art, competitors, market context) instead of asking. If any of these three is missing, ask about it before writing, in one message, three questions at most:

1. **User problem**: What problem does this solve? Who experiences it, and how painful is it?
2. **Target users**: Which user segment(s)? What's their current workaround?
3. **Success metrics**: How will we know this worked? What moves if we nail it?

Constraints, prior art, and scope preference are worth asking about only if the user wants the detailed version. If the user says "just write it", go ahead and mark the gaps as assumptions.

### Step 3: Generate the PRD

Apply the **create-prd** skill: its 8-section template, lean by default (about one to two pages). Write the detailed version only if the user asks for it. Start the document with:

```
## Product Requirements Document: [Feature Name]

**Author**: [user]
**Date**: [today]
**Status**: Draft
```

Then the eight sections: Summary, Contacts (if known), Background, Objective, Market Segment(s), Value Proposition(s), Solution, Release. Market Segments and Value Propositions are always included; each value proposition uses the 6-part template (Who, Why, What before, How, What after, Alternatives). Put what the first version will not do in Release, and what's still unknown in Solution → Assumptions and open questions.

### Step 4: Review and Iterate

After generating, say in one line what you left out on purpose, then offer:
- "Want the **detailed version**, or should I expand a specific section?"
- "Want me to **tighten the scope** further? I can challenge what really needs to be in the first version."
- "Should I **run a pre-mortem** on this PRD?"
- "Want me to **break this into user stories** for engineering?"
- "Should I **create a stakeholder update** to socialize this?"

Save the PRD as a markdown file to the user's workspace.

## Notes

- Be opinionated about scope — a tight PRD is better than an expansive vague one
- If the idea is too big, proactively suggest phasing and spec only Phase 1
- Non-goals are as important as goals — they prevent scope creep
- Success metrics must be specific: "improve NPS" is bad, "increase NPS from 32 to 45 within 90 days of launch" is good
- Open questions should be genuinely unresolved — don't list things you can answer from context
- If the user provides research, weave insights into the Background section with attribution

© Paweł Huryn · MIT · phuryn/pm-skills

Similar slash commands

All slash commands for Writing and docs →

From the same set120

The whole set →
review-resume review-resume is a Claude Code command that evaluates product manager resumes against best practices and gives three priority improvements with examples. CX Codex +1 ★ 28,211repo stars analyze-cohorts analyze-cohorts runs cohort retention analysis on CSV files or generates SQL frameworks to measure feature adoption. CX Codex +1 ★ 28,211repo stars transform-roadmap transform-roadmap is a Claude Code command that turns a feature list or existing roadmap into an outcome-led plan with success measures and strategic context for product planning. CX Codex +1 ★ 28,211repo stars market-product market-product is a Claude Code command that generates campaign ideas, positioning, value prop copy and product names. It supports launches, rebrands and competitive repositioning. CX Codex +1 ★ 28,211repo stars competitive-analysis The competitive-analysis slash command maps a market, compares direct and indirect competitors, and surfaces ways to position a product differently. CX Codex +1 ★ 28,211repo stars plan-okrs plan-okrs generates three OKR sets that connect team goals to company strategy. Each OKR pairs a qualitative objective with three to five measurable key results. CX Codex +1 ★ 28,211repo stars analyze-feedback analyze-feedback processes reviews, NPS surveys, and support tickets into structured markdown reports with sentiment metrics and recurring themes. CX Codex +1 ★ 28,211repo stars pre-mortem The pre-mortem command stress-tests a PRD, launch plan, or feature before release by finding failure risks and turning them into follow-up actions. CX Codex +1 ★ 28,211repo stars

Project sponsors

Companies that keep this analytics open