AI Prompts for Product Managers: 40+ Ready-to-Use Templates

TL;DR - Best AI Prompts for Product Managers

Looking for ready-to-use AI prompts for product management? This guide contains 40+ copy-paste prompts that work with ChatGPT, Claude, and Gemini. Each prompt includes placeholders you can customize for your product and organization. For foundational prompting skills, see the Prompt Engineering Fundamentals guide.

What’s included:

• PRD & Requirements Prompts — Generate comprehensive product requirement documents and feature specs
• User Story Prompts — Create user stories with acceptance criteria in minutes
• Research & Discovery Prompts — Conduct competitive analysis, user research synthesis, and customer interviews
• Prioritization Prompts — Apply RICE, MoSCoW, opportunity scoring, and ICE frameworks
• Metrics & Analytics Prompts — Define KPIs, analyze data, and create dashboards
• Stakeholder Communication — Write executive updates, release notes, and roadmap narratives
• Go-to-Market Prompts — Create launch plans, positioning, and sales enablement
• Strategy Prompts — Product vision, market analysis, and business cases
• Planning Prompts — Create OKRs, sprint goals, and quarterly roadmaps

💡 Pro tip: For best results, include context about your product, target users, market, and company goals. The more specific your context, the more tailored the output. For advanced prompting techniques, see the Advanced Prompt Engineering guide.

How to Use These PM Prompts

Each prompt below is ready to copy and paste. Here’s how they work:

1. Copy the entire prompt from the code block
2. Replace the placeholder comments (lines starting with # REPLACE:) with your actual content
3. Paste into ChatGPT, Claude, or your preferred AI
4. Get your result and iterate if needed

Adding Context for Better Results

Product management prompts work best with rich context:

=== PRODUCT CONTEXT (include in any prompt) ===
Product: [Your product name and one-line description]
Target Users: [Primary user personas]
Market: [B2B SaaS / B2C / Enterprise / Consumer]
Company Stage: [Startup / Growth / Enterprise]
Key Metrics: [North star metric, key KPIs]
Competitors: [Main competitors]

PRD & Requirements Prompts

Generate a Full PRD

Use this to create a comprehensive Product Requirements Document. For AI-powered workflow automation, see the AI-Powered Workflows guide.

You are a senior product manager. Create a detailed Product Requirements Document (PRD) for the following feature.

=== FEATURE OVERVIEW ===
Feature Name: 
# REPLACE: Name of the feature

Problem Statement: 
# REPLACE: What problem does this solve? Why now?

Target Users: 
# REPLACE: Who is this for? Be specific about the persona.

=== PRODUCT CONTEXT ===
Product: 
# REPLACE: Your product name and brief description

Current State: 
# REPLACE: How does this work today? What's the gap?

=== GENERATE PRD WITH THESE SECTIONS ===

1. **Executive Summary** (2-3 sentences)

2. **Problem Statement**
   - User pain points (with data if available)
   - Business impact
   - Why this matters now

3. **Goals & Success Metrics**
   - Primary goal
   - Key metrics (quantitative)
   - Success criteria
   - Leading vs lagging indicators

4. **User Stories** (5-7 stories)
   - In "As a [user], I want [action], so that [benefit]" format
   - With Given/When/Then acceptance criteria

5. **Functional Requirements**
   - Must-have features (P0)
   - Should-have features (P1)
   - Nice-to-have features (P2)

6. **Non-Functional Requirements**
   - Performance (response times, throughput)
   - Security & Privacy
   - Accessibility (WCAG compliance)
   - Scalability

7. **User Experience**
   - Key user flows
   - Edge cases and error states
   - Mobile considerations

8. **Out of Scope**
   - What this feature will NOT include
   - Future considerations

9. **Dependencies & Risks**
   - Technical dependencies
   - Team dependencies
   - Key risks and mitigations

10. **Timeline & Milestones**
    - Phase breakdown
    - Key milestones

11. **Open Questions**
    - Decisions needed
    - Stakeholder input required

Generate Feature Specification (Lightweight)

Use this for a quick spec when a full PRD is overkill.

Create a feature specification for the following:

=== FEATURE ===
Name: 
# REPLACE: Feature name

One-liner: 
# REPLACE: What it does in one sentence

=== CONTEXT ===
Product: 
# REPLACE: Product name

Why now: 
# REPLACE: Why are we building this?

Target users: 
# REPLACE: Who benefits?

=== GENERATE SPECIFICATION ===

## Feature: [Name]

### Problem
(2-3 sentences on the problem with user impact)

### Solution
(2-3 sentences on the approach)

### User Flow
1. (Step-by-step user journey)
2. ...

### Requirements
| Requirement | Priority | Notes |
|-------------|----------|-------|
| (requirement) | P0/P1/P2 | (details) |

### Acceptance Criteria
- [ ] Given [context], When [action], Then [result]
- [ ] ...

### Out of Scope
- (what's NOT included)

### Success Metrics
- (primary metric with target)
- (secondary metric)

### Open Questions
- (decisions needed)

Requirements Completeness Checker

Use this to identify gaps before development starts.

Review these requirements and identify gaps, ambiguities, and missing information.

=== REQUIREMENTS ===
# REPLACE: Paste your requirements document or feature description

=== CHECK FOR ===

1. **Ambiguous Language**
   - Vague terms like "fast," "easy," "seamless," "intuitive"
   - Missing specifics and numbers

2. **Missing Edge Cases**
   - Error states
   - Empty states
   - Boundary conditions
   - Concurrent user scenarios

3. **Incomplete User Flows**
   - Dead ends
   - Missing steps
   - Unclear transitions
   - Mobile vs desktop differences

4. **Undefined Business Rules**
   - Calculations without formulas
   - Rules without logic
   - Missing validation rules

5. **Missing Non-Functional Requirements**
   - Performance expectations
   - Security requirements
   - Accessibility needs
   - Internationalization

6. **Unstated Assumptions**
   - Things the requirements assume to be true

7. **Missing Dependencies**
   - External services
   - Other teams
   - Data requirements

=== OUTPUT FORMAT ===
For each issue found:
| Issue | Location | Recommendation | Priority |
|-------|----------|----------------|----------|
| (description) | (where) | (how to fix) | HIGH/MED/LOW |

API/Integration Requirements

Use this when your feature requires APIs or integrations.

Generate API and integration requirements for this feature.

=== FEATURE ===
# REPLACE: Feature description

=== INTEGRATIONS NEEDED ===
# REPLACE: List systems to integrate with
# - Payment gateway
# - CRM system
# - Email service
# - Analytics platform

=== GENERATE ===

## Integration Requirements

### Data Flow Diagram
(Describe how data flows between systems)

### API Requirements

| Endpoint | Method | Purpose | Request | Response |
|----------|--------|---------|---------|----------|
| (path) | GET/POST | (what it does) | (payload) | (response) |

### Integration Details

**[System Name]**
- Integration type: (API / Webhook / SDK / File)
- Authentication: (OAuth / API Key / JWT)
- Rate limits: (requests per minute)
- Error handling: (retry strategy)
- Data mapping: (field mappings)

### Security Requirements
- Authentication method
- Data encryption
- PII handling
- Audit logging

### Testing Requirements
- Test environment access
- Test data requirements
- Integration test scenarios

User Story Prompts

Generate User Stories from Feature

Use this to break down a feature into well-formed user stories.

Generate user stories for the following feature.

=== FEATURE ===
# REPLACE: Describe the feature

=== TARGET USERS ===
# REPLACE: List the user personas
# - Admin users who manage team settings
# - End users who consume content
# - API consumers integrating our service

=== GENERATE USER STORIES ===

For each user type, generate 3-5 user stories in this format:

**User Story [number]: [Title]**

As a [specific user persona],
I want to [action/capability],
So that [benefit/value].

**Acceptance Criteria:**
- Given [context]
- When [action]
- Then [expected outcome]
- And [additional outcome if applicable]

**Notes:**
- Edge cases to consider
- Dependencies
- Design considerations

---

Group stories by:
1. Core functionality (MVP)
2. Enhanced functionality
3. Edge cases and errors
4. Administrative/settings

**Story Point Estimates:** (relative sizing 1-8)

Convert Vague Request to User Stories

Use this when stakeholders give unclear feature requests.

Convert this feature request into actionable user stories.

=== ORIGINAL REQUEST ===
From: 
# REPLACE: Who requested this (e.g., Sales, CEO, Customer)

Request: 
# REPLACE: Paste the original feature request (even if vague)

=== CONTEXT ===
Product: 
# REPLACE: Your product

What we think they mean: 
# REPLACE: Your interpretation (or "Unclear")

=== GENERATE ===

## Analysis

### Clarified Problem Statement
- What problem is really being solved?
- Who has this problem?
- How painful is it? (frequency, severity)

### Questions for Stakeholder
1. (clarifying question)
2. (clarifying question)
3. (clarifying question)

### Assumptions Made
- (assumption 1)
- (assumption 2)

---

## Proposed User Stories

**MVP Scope:**
(minimum to address the request)

| Story | Acceptance Criteria Summary | Points |
|-------|---------------------------|--------|

**Full Scope:**
(complete solution)

| Story | Acceptance Criteria Summary | Points |

**Future Scope:**
(enhancements for later)

| Story | Why deferred |

---

### Recommendation
(which scope to pursue and why)

Epic Breakdown

Use this to break a large epic into shippable stories.

Break this epic into smaller, shippable user stories.

=== EPIC ===
Title: 
# REPLACE: Epic title

Description: 
# REPLACE: Epic description

Goal: 
# REPLACE: What success looks like

=== CONSTRAINTS ===
Sprint length: 
# REPLACE: e.g., 2 weeks

Team size: 
# REPLACE: e.g., 2 engineers, 1 designer

=== GENERATE ===

## Epic: [Title]

### Story Map

**User Activities (backbone):**
1. (core activity 1)
2. (core activity 2)
3. (core activity 3)

**User Tasks (under each activity):**
- Activity 1: task a, task b, task c
- Activity 2: task a, task b

### Release Plan

**Release 1 - MVP (Sprint X-Y)**
| Story | Points | Acceptance Criteria | Dependencies |
|-------|--------|---------------------|--------------|

**Release 2 - Enhanced (Sprint Y-Z)**
| Story | Points | Acceptance Criteria | Dependencies |

**Release 3 - Complete (Sprint Z+)**
| Story | Points | Acceptance Criteria | Dependencies |

### Dependencies Graph
- Story X blocks Story Y
- Story A and B can be parallel

### Risks
| Risk | Impact | Mitigation |
|------|--------|------------|

### Definition of Done (Epic Level)
- [ ] All stories complete
- [ ] Integration tested
- [ ] Documentation updated
- [ ] Metrics implemented

Research & Discovery Prompts

Competitive Analysis Framework

Use this for systematic competitor analysis.

Conduct a competitive analysis.

=== MY PRODUCT ===
Name: 
# REPLACE: Your product name

Description: 
# REPLACE: One-line description

Target market: 
# REPLACE: Who you serve

Key differentiators: 
# REPLACE: What makes you unique

Pricing: 
# REPLACE: Your pricing model

=== COMPETITORS ===
# REPLACE: List 3-5 competitors with brief descriptions

=== ANALYSIS FOCUS ===
# REPLACE: Check all that apply
# - [ ] Feature comparison
# - [ ] Pricing models
# - [ ] Target audience
# - [ ] Positioning/messaging
# - [ ] Strengths/weaknesses
# - [ ] Market share
# - [ ] Recent moves

=== GENERATE ===

## Competitive Analysis: [Your Product]

### Executive Summary
(3-4 sentences on competitive landscape)

### Feature Comparison Matrix
| Feature | Your Product | Comp A | Comp B | Comp C |
|---------|-------------|--------|--------|--------|
| (feature) | ✅/🟡/❌ | ✅/🟡/❌ | ✅/🟡/❌ | ✅/🟡/❌ |

### Positioning Map
(Describe 2x2 positioning on key dimensions)

### Competitor Deep Dives

**Competitor A: [Name]**
- Target Customer: 
- Strengths:
- Weaknesses:
- Pricing:
- Recent Moves:
- Our Positioning vs Them:

(Repeat for each competitor)

### SWOT Analysis (Your Product)
| Strengths | Weaknesses |
|-----------|------------|
| Opportunities | Threats |

### Market Gaps & Opportunities
1. (underserved need)
2. (market gap)
3. (emerging trend)

### Strategic Recommendations
1. **Defend:** (where to protect position)
2. **Attack:** (where to gain share)
3. **Differentiate:** (how to stand out)

User Research Synthesis

Use this to analyze user research data.

Synthesize this user research into actionable insights.

=== RESEARCH DATA ===
Research Type: 
# REPLACE: Interviews / Surveys / Usability tests / Support tickets

Number of participants: 
# REPLACE: e.g., 12 users

=== RAW FINDINGS ===
# REPLACE: Paste your research notes, quotes, or observations

=== GENERATE SYNTHESIS ===

## Research Synthesis

### Methodology Summary
- Type: (research type)
- Sample: (who and how many)
- Duration: (when conducted)

### Key Themes
| Theme | Frequency | Evidence | Implication |
|-------|-----------|----------|-------------|
| (theme) | X/Y users | "quote" | (action) |

### User Pain Points (Prioritized)
1. **(Critical)** [Pain Point] - Mentioned by X users
   - Quote: "..."
   - Impact: 
   
2. **(High)** [Pain Point] - Mentioned by X users

3. **(Medium)** [Pain Point]

### Jobs to Be Done
1. When [situation], I want to [motivation], so I can [outcome]
2. ...

### Unexpected Insights
- (Things that surprised us)

### Persona Validation
- Confirmed: (what matched our assumptions)
- Challenged: (what didn't match)
- New: (what we learned)

### Recommendations
| Priority | Recommendation | Evidence | Effort |
|----------|---------------|----------|--------|
| P0 | (must do) | (supporting data) | S/M/L |
| P1 | (should do) | | |
| P2 | (could do) | | |

### Open Questions
- (What we still need to learn)

### Next Research Steps
- (Follow-up research needed)

Customer Interview Guide

Use this to prepare for customer discovery interviews.

Create a customer interview guide.

=== RESEARCH OBJECTIVE ===
# REPLACE: What do you want to learn?
# Example: Understand how users currently manage their team's tasks

=== TARGET INTERVIEWEE ===
# REPLACE: Who are you interviewing?
# - Role: Project Manager
# - Company size: 50-200 employees
# - Usage: Active user for 3+ months

=== HYPOTHESES TO VALIDATE ===
# REPLACE: What do you believe to be true?
# 1. Users struggle with X
# 2. They currently solve it by Y

=== GENERATE INTERVIEW GUIDE ===

## Customer Interview Guide

### Pre-Interview
**Logistics:**
- Duration: 45-60 minutes
- Recording: (ask permission)
- Incentive: (if applicable)

**Materials needed:**
- Note-taking template
- Consent form
- Prototype/mockups (if testing)

### Introduction (5 min)
"Thanks for taking the time to chat. I'm [name], and I'm working on [area]. I'm here to learn from you—there are no right or wrong answers. Everything you share helps us build better products.

Before we start, do I have your permission to record this conversation for note-taking purposes?"

### Warm-up Questions (5 min)
1. Tell me about your role at [company].
2. How long have you been doing this work?
3. What does a typical day/week look like?

### Core Questions (30 min)

**Context Questions:**
1. Walk me through how you currently [relevant activity]...
2. What tools do you use for this?
3. How often do you do this?

**Pain Point Questions:**
4. What's the most frustrating part of [activity]?
5. Tell me about the last time [problem] happened...
6. How do you currently handle [challenge]?
7. What have you tried to solve this?

**Behavior Questions:**
8. When did you last [activity]? Walk me through it.
9. Who else is involved in this process?
10. What triggers you to [action]?

**Value Questions:**
11. What would make this easier?
12. If you could wave a magic wand, what would change?
13. How would that impact your work?

### Wrap-up (5 min)
14. Is there anything else you think I should know?
15. Who else should I talk to about this?
16. Can I follow up if I have more questions?

### Post-Interview
- Debrief notes within 24 hours
- Key quotes to capture
- Surprises and insights
- Updates to hypotheses

Build User Persona

Use this to create data-driven personas.

Create a detailed user persona based on this information.

=== RESEARCH INPUTS ===
# REPLACE: Paste any of the following:
# - Interview notes
# - Survey data
# - Analytics data
# - Customer support patterns
# - Sales call notes

=== PERSONA TYPE ===
# REPLACE: Primary / Secondary / Negative persona

=== GENERATE PERSONA ===

## Persona: [Name]

### Quick Summary
> "[One sentence that captures this persona]"

### Demographics
| Attribute | Value |
|-----------|-------|
| Name | (Fictional) |
| Role | |
| Company Size | |
| Industry | |
| Experience | |
| Age Range | |
| Location | |

### Goals & Motivations
1. **Primary Goal:** (what they're trying to achieve)
2. **Secondary Goal:** 
3. **Personal Motivation:** (career/emotional driver)

### Pain Points & Frustrations
1. **(Critical)** [Pain Point]
   - Frequency: Daily/Weekly/Monthly
   - Current workaround:
   
2. **(High)** [Pain Point]
3. **(Medium)** [Pain Point]

### Behaviors
- **Daily workflow:** (how they work)
- **Tools used:** (current tech stack)
- **Information sources:** (how they learn)
- **Decision process:** (how they evaluate)
- **Buying influence:** (decision maker/influencer/user)

### Quote
> "[Representative quote that captures this persona]"

### Day in the Life
(Narrative scenario showing when/how they'd use your product)

### What They Need From Us
1. (Capability 1)
2. (Capability 2)
3. (Capability 3)

### What Would Make Them Leave
- (churn triggers)

### How to Reach Them
- Channels: (where they spend time)
- Messaging: (what resonates)
- Objections: (what they'll push back on)

Prioritization Prompts

RICE Scoring

Use this to prioritize features using RICE.

Apply RICE scoring to prioritize these features.

=== RICE FRAMEWORK ===
- Reach: How many users affected per quarter?
- Impact: How much impact per user? (3=massive, 2=high, 1=medium, 0.5=low, 0.25=minimal)
- Confidence: How confident in estimates? (100%=high, 80%=medium, 50%=low)
- Effort: Person-months to complete

=== FEATURES TO SCORE ===
# REPLACE: List features to prioritize
# 1. Feature A - brief description
# 2. Feature B - brief description
# 3. Feature C - brief description

=== CONTEXT ===
Total users: 
# REPLACE: Active user count

Team capacity: 
# REPLACE: Available person-months per quarter

Company priorities:
# REPLACE: Current focus (growth, retention, revenue, etc.)

=== GENERATE RICE ANALYSIS ===

## RICE Prioritization

| Rank | Feature | Reach | Impact | Confidence | Effort | Score |
|------|---------|-------|--------|------------|--------|-------|
| 1 | (feature) | (num) | (0.25-3) | (50-100%) | (months) | (R*I*C/E) |

### Scoring Rationale

**#1: [Feature Name]** - Score: X
- **Reach:** X users/quarter
  - Rationale: (why this reach)
- **Impact:** X 
  - Rationale: (why this impact)
- **Confidence:** X%
  - Rationale: (why this confidence)
- **Effort:** X person-months
  - Rationale: (why this effort)

(Repeat for each feature)

### Recommendations

**Do First (Score > X):**
1. Feature A - because...

**Do Next (Score X-Y):**
1. Feature B

**Defer (Score < Y):**
1. Feature C - unless...

**Revisit:**
- Feature D: High potential but low confidence. Needs: (validation needed)

### Sensitivity Analysis
- If [assumption changes], Feature X would move from position Y to Z

ICE Scoring

Use this for quick prioritization with ICE framework.

Apply ICE scoring to prioritize these ideas.

=== ICE FRAMEWORK ===
- Impact: How much will this move the needle? (1-10)
- Confidence: How sure are we this will work? (1-10)
- Ease: How easy is this to implement? (1-10)

Score = (Impact + Confidence + Ease) / 3

=== IDEAS TO SCORE ===
# REPLACE: List ideas/experiments/features
# 1. Idea A
# 2. Idea B

=== GENERATE ICE ANALYSIS ===

## ICE Prioritization

| Rank | Idea | Impact | Confidence | Ease | ICE Score |
|------|------|--------|------------|------|-----------|
| 1 | (idea) | (1-10) | (1-10) | (1-10) | (avg) |

### Quick Wins (High ICE, Low Effort)
- (ideas to do immediately)

### Big Bets (High Impact, Lower Confidence)
- (ideas that need validation first)

### Easy Wins (Moderate Impact, Very Easy)
- (ideas for when you have spare capacity)

### Avoid (Low ICE)
- (ideas to deprioritize)

MoSCoW Prioritization

Use this to scope a release.

Apply MoSCoW prioritization to scope this release.

=== RELEASE CONTEXT ===
Release name: 
# REPLACE: e.g., "Q1 Launch", "MVP"

Timeline: 
# REPLACE: e.g., "6 weeks"

Goal: 
# REPLACE: What this release must achieve

=== FEATURE LIST ===
# REPLACE: List all features being considered

=== CONSTRAINTS ===
Engineering capacity: 
# REPLACE: e.g., "3 engineers for 6 weeks"

Dependencies: 
# REPLACE: Any external dependencies

=== GENERATE MoSCoW ===

## MoSCoW: [Release Name]

### Must Have (Non-negotiable)
| Feature | Effort | Why Must Have |
|---------|--------|---------------|
| (feature) | (days) | (reasoning) |

**Total Must Have Effort:** X weeks
**Fits Timeline:** ✅/❌

### Should Have (Important)
| Feature | Effort | Risk if Excluded |
|---------|--------|------------------|

### Could Have (Nice to have)
| Feature | Effort | Benefit |
|---------|--------|---------|

### Won't Have (Out of scope)
| Feature | Why Excluded | When to Revisit |
|---------|--------------|-----------------|

### Summary
- Must Have: X weeks (Y% of capacity)
- Should Have: X weeks (Y% of capacity)
- Buffer: X weeks
- Cut Line: After [feature], we're at capacity

### Risks
- What if Must Haves take longer?
- What if requirements change?

Opportunity Scoring

Use this for Opportunity Solution Tree prioritization.

Score these opportunities using the Opportunity-Solution Tree framework.

=== OPPORTUNITIES ===
# REPLACE: List opportunities (user needs/pain points)
# 1. Users struggle to find relevant content
# 2. Users forget to complete tasks
# 3. Users can't collaborate in real-time

=== PRODUCT VISION ===
# REPLACE: Your product's vision/north star

=== GENERATE OPPORTUNITY SCORES ===

## Opportunity Assessment

### Scoring Criteria
- **Importance:** How important is this to users? (1-5)
- **Satisfaction:** How satisfied are they with current solutions? (1-5)
- **Opportunity Score:** Importance + (Importance - Satisfaction)

| Opportunity | Importance | Satisfaction | Opp Score |
|-------------|------------|--------------|-----------|

### Opportunity Prioritization

**High Opportunity (Score > X):**
1. [Opportunity] - Score: X
   - Why high: 
   - Potential solutions:

**Medium Opportunity:**
...

**Low Opportunity:**
...

### Recommended Focus
Focus on [Opportunity X] because:
1. (reason)
2. (reason)

### Discovery Needed
For [Opportunity Y], we need to:
- Research: (what to learn)
- Validate: (how to test)

Metrics & Analytics Prompts

Define Success Metrics

Use this to define how you’ll measure feature success.

Define success metrics for this feature.

=== FEATURE ===
# REPLACE: Feature description

=== BUSINESS GOAL ===
# REPLACE: What business outcome should this drive?
# (increase revenue, reduce churn, improve engagement, etc.)

=== USER GOAL ===
# REPLACE: What user outcome should this enable?

=== GENERATE METRICS FRAMEWORK ===

## Success Metrics: [Feature Name]

### Primary Metric (North Star)
**Metric:** [name]
- Definition: (exactly how it's calculated)
- Current baseline: (current value)
- Target: (goal value)
- Timeframe: (when to measure)

### Secondary Metrics

| Type | Metric | Definition | Target |
|------|--------|------------|--------|
| Adoption | | (how many use it) | |
| Engagement | | (how often/deeply) | |
| Retention | | (do they come back) | |
| Satisfaction | | (NPS, CSAT, etc.) | |
| Business | | (revenue impact) | |

### Leading Indicators
(Metrics that predict success early)
1. [Metric] - signals [outcome]
2. ...

### Guardrail Metrics
(Metrics that shouldn't go down)
1. [Metric] - must stay above [threshold]
2. ...

### Counter Metrics
(Potential negative effects to watch)
1. [Metric] - could decrease if we over-optimize for primary
2. ...

### Measurement Plan
| Metric | Data Source | Tracking Method | Owner |
|--------|-------------|-----------------|-------|

### Success Criteria
- **Launch goals:** (week 1-2)
- **Short-term goals:** (month 1)
- **Long-term goals:** (quarter 1)

### When to Iterate vs Kill
- **Iterate if:** (conditions)
- **Kill if:** (conditions)

Analyze Metrics Performance

Use this to analyze how a feature or product is performing.

Analyze these metrics and provide insights.

=== METRICS DATA ===
# REPLACE: Paste your metrics data
# - DAU: 10,000 → 12,000 (last 30 days)
# - Conversion: 2.5% → 2.8%
# - Churn: 5% → 4.5%
# - NPS: 32 → 38

=== CONTEXT ===
# REPLACE: What happened during this period?
# - Launched feature X
# - Changed pricing
# - Marketing campaign

=== TIME PERIOD ===
# REPLACE: What dates/comparison period?

=== GENERATE ANALYSIS ===

## Metrics Analysis: [Period]

### Executive Summary
(3-4 sentences on overall performance)

### Key Metrics Dashboard

| Metric | Previous | Current | Change | Status |
|--------|----------|---------|--------|--------|
| (metric) | (value) | (value) | +/-% | 🟢/🟡/🔴 |

### What's Working ✅
1. **[Metric/Area]:** +X%
   - Why: (analysis of cause)
   - Action: (how to amplify)

2. ...

### What Needs Attention ⚠️
1. **[Metric/Area]:** -X%
   - Why: (analysis of cause)
   - Action: (how to address)

2. ...

### Correlations & Insights
- [Metric A] appears correlated with [Metric B]
- [Change] seems to have impacted [Metric]
- Unexpected: [observation]

### Recommendations

| Priority | Action | Expected Impact | Effort |
|----------|--------|-----------------|--------|
| P0 | (action) | (metric impact) | S/M/L |
| P1 | | | |

### Questions to Investigate
1. (follow-up analysis needed)
2. (experiment to run)

### Next Review
- Date: 
- Metrics to watch:

Stakeholder Communication Prompts

Executive Status Update

Use this for concise leadership updates.

Write an executive status update.

=== UPDATE PERIOD ===
# REPLACE: Week of X, Month of X, Q1, etc.

=== KEY UPDATES ===
# REPLACE: List major updates
# - Launched X
# - Progress on Y
# - Issue with Z

=== METRICS ===
# REPLACE: Key metrics
# - DAU: 10K (+5%)
# - Revenue: $100K (+10%)

=== BLOCKERS/RISKS ===
# REPLACE: Issues leadership should know

=== AUDIENCE ===
# REPLACE: CEO / VP / Board / All-hands

=== GENERATE UPDATE ===

## [Product] Update - [Period]

### TL;DR
(2-3 sentences: key win, key challenge, what's next)

### Scorecard
| Metric | Actual | Target | Status |
|--------|--------|--------|--------|
| | | | 🟢/🟡/🔴 |

### Key Accomplishments ✅
1. (achievement with impact)
2. (achievement)

### In Progress 🔄
| Initiative | Status | ETA | Notes |
|------------|--------|-----|-------|

### Risks & Blockers 🚨
| Issue | Impact | Mitigation | Need |
|-------|--------|------------|------|

### Decisions Needed
- (decision required from leadership)

### Next Period Focus
1. (priority 1)
2. (priority 2)

Release Notes Writer

Use this for user-facing release notes.

Write release notes for this product update.

=== RELEASE INFO ===
Version: 
# REPLACE: e.g., 2.5.0

Release Date: 
# REPLACE: Date

=== CHANGES ===
# REPLACE: List all changes
# - Added feature X
# - Fixed bug Y 
# - Improved Z

=== AUDIENCE ===
# REPLACE: End users / Admins / Developers

=== TONE ===
# REPLACE: Casual / Professional / Technical

=== GENERATE RELEASE NOTES ===

# What's New in [Version]

## ✨ New Features

### [Feature Name]
(2-3 sentences: what it does and why it matters)

**Getting started:** (how to use it)

## 🚀 Improvements
- **[Area]:** (what's better)

## 🐛 Bug Fixes
- Fixed an issue where (user-facing description)

## 📝 Notes
- (breaking changes, migration steps)

## Coming Soon
- (preview of what's next)

---

Questions? [Contact support](link)

Feature Announcement (Multi-Channel)

Use this for feature launches across channels.

Write a feature announcement for multiple channels.

=== FEATURE ===
Name: 
# REPLACE: Feature name

What it does: 
# REPLACE: Feature description

Who it's for: 
# REPLACE: Target users

Key benefit: 
# REPLACE: Main value proposition

Available: 
# REPLACE: Date / Already live

=== GENERATE ANNOUNCEMENTS ===

## 1. Email Announcement

**Subject Lines (A/B test):**
1. (option 1)
2. (option 2)

**Body:**
(Complete email)

---

## 2. In-App Notification
(Max 100 characters)

---

## 3. Product Blog Post

### [Headline]

(800-word blog post with:)
- Hook
- Problem
- Solution
- How it works
- Getting started
- CTA

---

## 4. Social Media

**LinkedIn:** (150-200 words, professional)

**Twitter/X:** (280 chars, punchy)

---

## 5. Sales Enablement

**One-pager for sales:**
- What: 
- Who: 
- Value prop:
- Pricing impact:
- Competition:
- Objection handling:
- Demo talking points:

Roadmap Presentation

Use this to present roadmap to different audiences.

Create a roadmap presentation for this audience.

=== ROADMAP ===
# REPLACE: Paste your roadmap (themes, features, timeline)

=== AUDIENCE ===
# REPLACE: Executive team / Engineering / Customers / Board

=== GOAL ===
# REPLACE: What do you want from this presentation?
# - Approval for direction
# - Buy-in from engineering
# - Customer confidence
# - Board update

=== GENERATE PRESENTATION ===

## Roadmap Presentation: [Audience]

### Opening (1 slide)
**Title:** [Product Name] Roadmap - [Period]
**Hook:** (compelling opening statement)

### Context (1-2 slides)
- Where we are today
- Key metrics
- Customer feedback themes
- Market changes

### Vision (1 slide)
- Where we're going
- Why it matters

### Roadmap Overview (1-2 slides)

| Timeline | Theme | Key Deliverables | Impact |
|----------|-------|-----------------|--------|
| Q1 | | | |
| Q2 | | | |

### Deep Dive: [Top Priority] (2-3 slides)
- Problem
- Solution
- Expected impact
- Timeline
- Dependencies

### What We're NOT Doing (1 slide)
- Deprioritized items
- Why

### Risks & Dependencies (1 slide)
| Risk | Mitigation |
|------|------------|

### Ask (1 slide)
What you need from this audience

### Q&A Prep
Likely questions and answers:
1. Q: ... A: ...

Go-to-Market Prompts

GTM Launch Plan

Use this to create a go-to-market launch plan.

Create a go-to-market launch plan.

=== PRODUCT/FEATURE ===
Name: 
# REPLACE: What you're launching

Description: 
# REPLACE: What it does

=== TARGET MARKET ===
Primary segment: 
# REPLACE: Who is the ideal customer

Secondary segment: 
# REPLACE: Who else might buy

=== LAUNCH DATE ===
# REPLACE: Target date

=== GOALS ===
# REPLACE: Launch goals
# - X signups in first week
# - X revenue in first month
# - X press mentions

=== GENERATE GTM PLAN ===

## GTM Launch Plan: [Product Name]

### Executive Summary
(Launch objectives in 3-4 sentences)

### Launch Goals & Metrics
| Goal | Metric | Target | Timeline |
|------|--------|--------|----------|

### Target Audience

**Primary Segment:**
- Who: 
- Pain point:
- Why now:
- How to reach:

**Secondary Segment:**
...

### Positioning & Messaging

**Positioning Statement:**
For [target customer] who [need], [product] is a [category] that [key benefit]. Unlike [competitor], we [differentiator].

**Key Messages:**
1. (message for segment A)
2. (message for segment B)

**Proof Points:**
- (statistic/case study)

### Launch Timeline

| Date | Milestone | Owner | Status |
|------|-----------|-------|--------|
| T-4 weeks | | | |
| T-2 weeks | | | |
| Launch day | | | |
| T+1 week | | | |

### Channel Strategy

| Channel | Content/Activity | Goal | Budget |
|---------|-----------------|------|--------|
| Email | | | |
| Social | | | |
| Press | | | |
| Paid | | | |
| Product | | | |

### Sales Enablement
- Training date:
- Materials needed:
- Objection handling:
- Pricing guidance:

### Success Metrics Dashboard
| Metric | Day 1 | Week 1 | Month 1 |
|--------|-------|--------|---------|

### Risk Mitigation
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|

### Post-Launch Plan
- Week 1: (activities)
- Week 2-4: (activities)
- Month 2+: (activities)

Positioning Statement Generator

Use this to craft compelling positioning.

Create a positioning statement and messaging framework.

=== PRODUCT ===
Name: 
# REPLACE: Product name

Description: 
# REPLACE: What it does

=== TARGET CUSTOMER ===
# REPLACE: Who is it for

=== PROBLEM ===
# REPLACE: What problem does it solve

=== COMPETITORS ===
# REPLACE: Main alternatives

=== DIFFERENTIATORS ===
# REPLACE: What makes you unique

=== GENERATE POSITIONING ===

## Positioning Framework

### Core Positioning Statement
For [target customer] who [has this need/problem],
[Product name] is a [category] that [key benefit].
Unlike [main competitor/alternative], [product name] [key differentiator].

### Elevator Pitch (30 seconds)
(Conversational version of positioning)

### Tagline Options
1. (option 1)
2. (option 2)
3. (option 3)

### Value Pillars

| Pillar | What We Do | Why It Matters | Proof |
|--------|-----------|----------------|-------|
| 1 | | | |
| 2 | | | |
| 3 | | | |

### Messaging by Audience

**For [Persona 1]:**
- Lead with: (primary message)
- Support with: (proof points)
- Avoid: (what not to say)

**For [Persona 2]:**
...

### Competitive Differentiation

| Differentiator | Us | Competitor A | Competitor B |
|---------------|-----|--------------|--------------|

### Objection Handling
| Objection | Response |
|-----------|----------|
| "Too expensive" | |
| "We already use X" | |

Planning Prompts

Create Quarterly OKRs

Use this to generate OKRs.

Generate OKRs for the upcoming quarter.

=== CONTEXT ===
Quarter: 
# REPLACE: Q1 2025, etc.

Product/Team: 
# REPLACE: Product name or team

=== COMPANY PRIORITIES ===
# REPLACE: Top company goals this quarter

=== LAST QUARTER RESULTS ===
# REPLACE: What was achieved or missed

=== FOCUS AREAS ===
# REPLACE: What the team should focus on

=== GENERATE OKRs ===

## [Team] OKRs - [Quarter]

### Objective 1: [Inspiring, qualitative statement]
**Why this matters:** (context)

**Key Results:**
1. Increase [metric] from [X] to [Y]
   - Current: X
   - Target: Y
   - Confidence: High/Med/Low
   
2. Achieve [measurable outcome]
   - How measured:
   - Target:
   
3. [Third key result]

**Initiatives:** (what we'll do)
- Initiative A
- Initiative B

**Dependencies:** (what could block us)

---

### Objective 2: [Inspiring statement]
...

---

## OKR Summary

| Objective | KR1 | KR2 | KR3 | Owner |
|-----------|-----|-----|-----|-------|

## Alignment Check
Company Goal → Team OKR: (how connected)

## Review Cadence
- Weekly: Check-in on KR progress
- Monthly: Deep dive on blockers
- End of quarter: Scoring and retro

Sprint Goal Writer

Use this for clear sprint goals.

Write a sprint goal.

=== SPRINT INFO ===
Sprint: 
# REPLACE: Sprint number

Duration: 
# REPLACE: 2 weeks

=== PLANNED WORK ===
# REPLACE: What's in the sprint
# - Story 1
# - Story 2
# - Story 3

=== CONSTRAINTS ===
# REPLACE: Limitations (PTO, dependencies, etc.)

=== GENERATE SPRINT GOAL ===

## Sprint [Number] Goal

### Goal Statement
"By the end of this sprint, [users/stakeholders] will be able to [capability] which will [business impact]."

### Success Criteria
- [ ] (Testable criterion 1)
- [ ] (Testable criterion 2)
- [ ] (Testable criterion 3)

### What Done Looks Like
(Concrete description of end state)

### Out of Scope
- (What we're NOT doing this sprint)

### Risks
| Risk | Likelihood | Mitigation |
|------|------------|------------|

### Demo Preview
(What we'll show at sprint review)

### Team Commitment
Capacity: X story points
Committed: Y story points
Buffer: Z points (for unknowns)

Roadmap Theme Generator

Use this to organize features into themes.

Organize these features into roadmap themes.

=== FEATURE BACKLOG ===
# REPLACE: List features
# 1. Feature A
# 2. Feature B
# ...

=== STRATEGIC CONTEXT ===
Vision: 
# REPLACE: Product vision

Annual priorities: 
# REPLACE: Top priorities

Target customers: 
# REPLACE: Who you're building for

=== GENERATE THEMED ROADMAP ===

## Product Roadmap Themes

### Now (Current Quarter)

**Theme: [Name]**
- Narrative: (why this theme, why now)
- Features: 1, 2, 3
- Success metric:
- Status: In Progress

### Next (Next Quarter)

**Theme: [Name]**
- Narrative:
- Features:
- Success metric:
- Dependencies:

### Later (Future)

**Theme: [Name]**
...

---

## Visual Roadmap

| Quarter | Theme | Key Milestones |
|---------|-------|----------------|
| Q1 | | |
| Q2 | | |

## Theme Dependencies
- Theme X enables Theme Y
- Theme Z requires Theme W first

## What's NOT on the Roadmap
- Feature N: Why deferred
- Request M: Why declined

Strategy Prompts

Product Vision Statement

Use this to articulate product vision.

Create a product vision statement.

=== PRODUCT ===
Name: 
# REPLACE: Product name

Current state: 
# REPLACE: What it does today

=== COMPANY CONTEXT ===
Mission: 
# REPLACE: Company mission

Target market: 
# REPLACE: Who you serve

=== TIME HORIZON ===
# REPLACE: 3 years / 5 years

=== GENERATE VISION ===

## Product Vision

### Vision Statement
(One inspiring sentence about the future state)

### Vision Narrative
(2-3 paragraph description of what the world looks like when we achieve the vision)

### Strategic Pillars
How we'll get there:

1. **[Pillar 1]:** (capability we'll build)
2. **[Pillar 2]:** 
3. **[Pillar 3]:**

### Success Looks Like
In [time horizon]:
- Users: (who and how many)
- Revenue: (scale)
- Product: (capabilities)
- Market: (position)

### What We Believe
Core assumptions:
1. (belief about market)
2. (belief about users)
3. (belief about technology)

### Risks to Vision
| Risk | Mitigation |
|------|------------|

Build vs Buy Analysis

Use this when deciding whether to build or buy.

Analyze build vs buy vs partner for this capability.

=== CAPABILITY NEEDED ===
# REPLACE: What do you need to do?

=== OPTIONS ===
Build: 
# REPLACE: Build it yourself

Buy: 
# REPLACE: Vendor options

Partner: 
# REPLACE: Partnership options

=== CONTEXT ===
Timeline: 
# REPLACE: When do you need it

Budget: 
# REPLACE: Available budget

Team capacity: 
# REPLACE: Engineering availability

Strategic importance: 
# REPLACE: How core is this to your product

=== GENERATE ANALYSIS ===

## Build vs Buy Analysis: [Capability]

### Executive Summary
Recommendation: [Build / Buy / Partner]
(3-4 sentences on why)

### Option Comparison

| Criteria | Build | Buy | Partner |
|----------|-------|-----|---------|
| Time to value | | | |
| Upfront cost | | | |
| Ongoing cost | | | |
| Customization | | | |
| Control | | | |
| Risk | | | |
| Strategic fit | | | |

### Detailed Analysis

**Build Option:**
- Effort: X person-months
- Timeline: X months
- Pros:
- Cons:
- Risks:
- Best if: (conditions)

**Buy Option: [Vendor]**
- Cost: $X/month
- Implementation: X weeks
- Pros:
- Cons:
- Risks:
- Best if:

**Partner Option:**
...

### Recommendation
Choose [option] because:
1. (reason)
2. (reason)

### Decision Criteria Weighting
| Criteria | Weight | Build | Buy | Partner |
|----------|--------|-------|-----|---------|
| (criteria) | X% | score | score | score |
| **Total** | 100% | | | |

### Reversibility
How hard is it to change course later?

Quick Reference

Tips for Better PM Prompts

1. Include Rich Product Context

❌ "Write a PRD for notifications"
✅ "Write a PRD for in-app notifications for our B2B SaaS project management tool. 
    Target users are project managers at mid-size companies who need to stay 
    updated on task changes without email overload."

2. Specify Your Audience

❌ "Write release notes"
✅ "Write release notes for end users (non-technical product managers), 
    keeping language simple and focusing on benefits over features."

3. Include Constraints

❌ "Prioritize these features"
✅ "Prioritize these features given we have 2 engineers for 6 weeks, 
    our goal is reducing churn by 10%, and we're a Series A startup."

4. Reference Frameworks

"Use RICE scoring..."
"Apply Jobs to Be Done framework..."
"Structure as an Amazon-style Working Backwards document..."

5. Ask for Alternatives

"Provide 3 options for [X] with trade-offs for each"
"What are the risks if we don't do this?"

6. Iterate Purposefully

"Good, but make the metrics more specific with baseline and target"
"Rewrite for a technical audience"
"Add more detail on the competitive differentiation"

7. Request Formats

"Output as a table..."
"Create a one-pager I can share..."
"Format for Notion/Confluence..."

Workflow Chains

Discovery to Delivery Workflow

WORKFLOW: Feature Discovery to Delivery

=== FEATURE IDEA ===
# REPLACE: The feature you're exploring

Follow these steps. Say "next" after each step.

STEP 1: Discovery
- Define problem statement
- Identify target users
- List assumptions to validate

STEP 2: Research  
- Create interview guide
- Define research questions
- List competitors to analyze

STEP 3: Definition
- Write user stories
- Define acceptance criteria
- Create success metrics

STEP 4: Specification
- Generate PRD
- Prioritize requirements
- Identify dependencies

STEP 5: Communication
- Create stakeholder update
- Draft announcement plan
- Prepare engineering handoff

Start with STEP 1.

What’s Next

• 📚 AI Prompts for Software Developers — Pair with your dev team
• 📚 Advanced Prompt Engineering — Master prompting techniques
• 📚 Prompt Engineering Fundamentals — Start with the basics
• 🛠️ PRD Generator Tool — Generate PRDs with guided AI
• 🛠️ Agile Epic Generator — Create epics and user stories

Found these prompts helpful? Share them with your product team!