Sign in
Explore
Prompts · PromptBusiness & OpsProduct managementReviewed

write-prd

Creates a lean Product Requirements Document from a feature idea or problem statement, with a fuller spec on request.

Kind
Prompt
Works with
Claude Code, Cursor
Source
PM Skills (Pawel Huryn) @ 2a12295a7717
Path
pm-execution/commands/write-prd.md
Jobs
Documentation, Planning
Topics
Product management

Credit

Made by
phuryn
Original
github.com/phuryn/pm-skills/blob/2a12295a7717569baa7be181b4cf…
License
MIT

Listed by Skill Manifest; not made by us.

InstallInstall it from a plugin marketplace.
claude plugin install pm-execution@pm-skills
Install factsScanned 2 Nov 2026
Adds
  • .claude/commands/write-prd.md (run as /write-prd)
Runs scripts
None found
Uses the network
None found
Needs secrets
None found
Source revision
2a12295a7717
Licence
MIT
Last activity
29 Oct 2026
Review
Reviewed

Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.

# /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?
…