Skill

create-prd

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

From pm-execution

Install

Run in your terminal

npx claudepluginhub tarunccet/pm-skills

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitMar 31, 2026

Actions

View Source View Plugin View on GitHub View README

create-prd

From pm-execution

Create a Product Requirements Document

What You'll Need

Input	Required?	Example
Feature idea or problem statement	✅ Required	"Smart notification batching to reduce alert fatigue"
Target user segment	✅ Required	Enterprise teams using Slack integrations
Business objective or outcome	✅ Required	Reduce notification-driven churn by 15%
User research or discovery findings	🟡 Recommended	Interview quotes, NPS feedback, usage data
Technical constraints	⚪ Optional	Existing API limits, platform restrictions

Input

Required?

Example

Feature idea or problem statement

✅ Required

"Smart notification batching to reduce alert fatigue"

Target user segment

✅ Required

Enterprise teams using Slack integrations

Business objective or outcome

✅ Required

Reduce notification-driven churn by 15%

User research or discovery findings

🟡 Recommended

Interview quotes, NPS feedback, usage data

Technical constraints

⚪ Optional

Existing API limits, platform restrictions

Don't have everything? Start anyway — the skill will work with what you provide and flag where richer input would improve the output.

Instructions

Gather Information: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.

Think Step by Step: Before writing, analyze:

What problem are we solving?
Who are we solving it for?
How will we measure success?
What are our constraints and assumptions?

Apply the PRD Template: Create a document with these 8 sections:

1. Summary (2-3 sentences)

What is this document about?

2. Contacts

Name, role, and comment for key stakeholders

3. Background

Context: What is this initiative about?
Why now? Has something changed?
Is this something that just recently became possible?

4. Objective

What's the objective? Why does it matter?
How will it benefit the company and customers?
How does it align with vision and strategy?
Key Results: How will you measure success? (Use SMART OKR format)

5. Market Segment(s)

For whom are we building this?
What constraints exist?
Note: Markets are defined by people's problems/jobs, not demographics

6. Value Proposition(s)

What customer jobs/needs are we addressing?
What will customers gain?
Which pains will they avoid?
Which problems do we solve better than competitors?
Consider the Value Curve framework

7. Solution

7.1 UX/Prototypes (wireframes, user flows)
7.2 Key Features (detailed feature descriptions)
7.3 Technology (optional, only if relevant)
7.4 Assumptions (what we believe but haven't proven)
7.5 AI/ML Considerations (include this section when the feature uses AI/ML)
- Model or API being used (e.g., GPT-4o, Gemini, custom model)
- Desired inputs and expected outputs (include example pairs)
- Confidence thresholds and fallback behaviour when AI fails or is uncertain
- Human-in-the-loop requirements (where does a human review/override?)
- Accuracy floor and latency SLO
- Data requirements and privacy constraints
- Responsible AI notes: known bias risks, content safety, explainability needs

8. Release

How long could it take?
What goes in the first version vs. future versions?
Avoid exact dates; use relative timeframes

Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.

Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.

Save the Output: If the PRD is substantial (which it will be), save it as a markdown document in the format: PRD-[product-name].md

Create a Product Requirements Document

What You'll Need

Input	Required?	Example
Feature idea or problem statement	✅ Required	"Smart notification batching to reduce alert fatigue"
Target user segment	✅ Required	Enterprise teams using Slack integrations
Business objective or outcome	✅ Required	Reduce notification-driven churn by 15%
User research or discovery findings	🟡 Recommended	Interview quotes, NPS feedback, usage data
Technical constraints	⚪ Optional	Existing API limits, platform restrictions

Input

Required?

Example

Feature idea or problem statement

✅ Required

"Smart notification batching to reduce alert fatigue"

Target user segment

✅ Required

Enterprise teams using Slack integrations

Business objective or outcome

✅ Required

Reduce notification-driven churn by 15%

User research or discovery findings

🟡 Recommended

Interview quotes, NPS feedback, usage data

Technical constraints

⚪ Optional

Existing API limits, platform restrictions

Don't have everything? Start anyway — the skill will work with what you provide and flag where richer input would improve the output.

Instructions

Gather Information: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.

Think Step by Step: Before writing, analyze:

What problem are we solving?
Who are we solving it for?
How will we measure success?
What are our constraints and assumptions?

Apply the PRD Template: Create a document with these 8 sections:

1. Summary (2-3 sentences)

What is this document about?

2. Contacts

Name, role, and comment for key stakeholders

3. Background

Context: What is this initiative about?
Why now? Has something changed?
Is this something that just recently became possible?

4. Objective

What's the objective? Why does it matter?
How will it benefit the company and customers?
How does it align with vision and strategy?
Key Results: How will you measure success? (Use SMART OKR format)

5. Market Segment(s)

For whom are we building this?
What constraints exist?
Note: Markets are defined by people's problems/jobs, not demographics

6. Value Proposition(s)

What customer jobs/needs are we addressing?
What will customers gain?
Which pains will they avoid?
Which problems do we solve better than competitors?
Consider the Value Curve framework

7. Solution

7.1 UX/Prototypes (wireframes, user flows)
7.2 Key Features (detailed feature descriptions)
7.3 Technology (optional, only if relevant)
7.4 Assumptions (what we believe but haven't proven)
7.5 AI/ML Considerations (include this section when the feature uses AI/ML)
- Model or API being used (e.g., GPT-4o, Gemini, custom model)
- Desired inputs and expected outputs (include example pairs)
- Confidence thresholds and fallback behaviour when AI fails or is uncertain
- Human-in-the-loop requirements (where does a human review/override?)
- Accuracy floor and latency SLO
- Data requirements and privacy constraints
- Responsible AI notes: known bias risks, content safety, explainability needs

8. Release

How long could it take?
What goes in the first version vs. future versions?
Avoid exact dates; use relative timeframes

Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.

Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.

Save the Output: If the PRD is substantial (which it will be), save it as a markdown document in the format: PRD-[product-name].md

create-prd

create-prd

Create a Product Requirements Document

What You'll Need

Purpose

Context

Instructions

Notes

Create a Product Requirements Document

What You'll Need

Purpose

Context

Instructions

Notes