Creates a structured Product Requirements Document from a feature idea or problem statement by gathering context conversationally.
From pm-executionnpx claudepluginhub bowiemax/pm-skills --plugin pm-execution<feature or problem statement>/write-prdCreates a structured Product Requirements Document from a feature idea or problem statement by gathering context conversationally.
/write-prdGenerates Product Requirements Documents (PRDs) using 8-section templates with user stories, INVEST criteria, acceptance criteria, and release plans. Outputs PRD-[product].md; choose full PRD, lightweight spec, stories only, or update.
/write-prdCreates a structured Product Requirements Document from a feature idea or problem statement by gathering context conversationally.
/write-prdTransform a conversation or idea into a structured PRD with user stories
Create a structured PRD that aligns stakeholders and guides development. Accepts anything from a vague idea to a detailed brief.
/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]
Accept the input in any form:
Ask conversationally — most important questions first, fill gaps as you go:
If the user provides a document with context, extract what's available and only ask about gaps.
Apply the create-prd skill to produce an 8-section document:
## Product Requirements Document: [Feature Name]
**Author**: [user]
**Date**: [today]
**Status**: Draft
**Stakeholders**: [if known]
### 1. Executive Summary
[2-3 sentences: what, for whom, why now]
### 2. Background & Context
[Problem space, prior research, market context, what prompted this]
### 3. Objectives & Success Metrics
**Goals** (what success looks like):
1. [Specific, measurable goal]
2. [...]
**Non-Goals** (explicitly out of scope):
1. [What we're not doing, and why]
2. [...]
**Success Metrics**:
| Metric | Current | Target | Measurement |
|--------|---------|--------|-------------|
### 4. Target Users & Segments
[Who this serves, user profiles, segment sizing]
### 5. User Stories & Requirements
**P0 — Must Have**:
| # | User Story | Acceptance Criteria |
|---|-----------|-------------------|
**P1 — Should Have**:
| # | User Story | Acceptance Criteria |
|---|-----------|-------------------|
**P2 — Nice to Have / Future**:
| # | User Story | Acceptance Criteria |
|---|-----------|-------------------|
### 6. Solution Overview
[High-level approach, key design decisions, technical approach if known]
### 7. Open Questions
| Question | Owner | Deadline |
|----------|-------|----------|
### 8. Timeline & Phasing
[Milestones, dependencies, phasing if applicable]
After generating, offer:
Save the PRD as a markdown file to the user's workspace.