I Built 25 ChatGPT Prompts for Product Managers - Why Most PMs Use ChatGPT Wrong
The problem with most PM-ChatGPT workflows Most product managers paste their problem into ChatGPT and hope for the best. They get generic output, spend 20 minutes rewriting, and conclude "AI isn't ready for PM work." The problem isn't ChatGPT. It's the prompts. After building prompt packs for developers, freelancers, and content creators (and seeing actual downloads on Gumroad), I decided to tackle the PM workflow. The result: 25 prompts that cover the full product management lifecycle from disc
The problem with most PM-ChatGPT workflows
Most product managers paste their problem into ChatGPT and hope for the best. They get generic output, spend 20 minutes rewriting, and conclude "AI isn't ready for PM work."
The problem isn't ChatGPT. It's the prompts.
After building prompt packs for developers, freelancers, and content creators (and seeing actual downloads on Gumroad), I decided to tackle the PM workflow. The result: 25 prompts that cover the full product management lifecycle from discovery to delivery.
What I built
Each prompt has bracketed placeholders. You paste in your specific context, hit enter, and get output you can actually use not generic fluff.
The 25 prompts span 5 categories:
1. Discovery and Research (5 prompts)
- Problem Space Mapper - Maps pain points by severity, creates JTBD frameworks, identifies competitor gaps
- Competitive Analysis - Builds a positioning comparison matrix with differentiation opportunities
- User Interview Questions - 15 structured questions across rapport, discovery, and validation phases
- Market Sizing - Three estimation approaches (top-down, bottom-up, value-based) with assumption highlighting
- Feature Prioritization - RICE scoring with effort estimation and combination flags
2. Specs and Documentation (5 prompts)
- PRD Generator - Full PRD with user stories, acceptance criteria, edge cases, and phased rollout
- User Story Breakdown - 10-15 stories by user journey step with dependency flags
- Technical Handoff Brief - API contracts, NFRs, and open questions for engineering
- API Specification - REST endpoints with JSON schemas, auth, error codes, pagination
- Release Notes - Internal and customer-facing formats, each under 200 words
3. Meetings and Communication (5 prompts)
- Sprint Planning Agenda - Time-boxed with goal review, backlog, capacity check
- Stakeholder Updates - Concise weekly email tailored to your audience
- Difficult Conversations - Scripted approach for scope cuts, deadline pushes, conflicts
- Product Review Presentations - 10-12 slide structure with anticipated Q and A
- Cross-Functional Alignment - One-pager mapping team contributions and conflicts
4. Analytics and Metrics (5 prompts)
- North Star Metric - Proposes metric with input metrics, guardrails, team connections
- A/B Test Plans - Sample size, duration, segments, confounders, decision criteria
- Retention Analysis - Diagnoses onboarding vs activation vs re-engagement issues
- Dashboard Design - Panel layout, visualization types, drill paths
- GTM Launch Metrics - Pre-launch, launch, post-launch checklist
5. Strategy and Roadmapping (5 prompts)
- OKR Drafting - 3 objectives with measurable KRs and conflict flags
- Build vs Buy - TCO, time to value, vendor lock-in analysis
- Feature Flag Rollout - Dogfooding, canary, gradual, full with rollback criteria
- PLG Playbook - Growth loops, onboarding fixes, aha moments, upgrade prompts
- Quarterly Roadmap Narrative - Executive summary with theme, pillars, and non-goals
The key insight: chain prompts together
The real power isn't in any single prompt. It's in chaining them. Use discovery prompts first to understand the problem space, feed those insights into spec prompts, then use communication prompts to share your work.
Example workflow for a new feature:
- Problem Space Mapper to understand the user problem
- Competitive Analysis to find the differentiation angle
- Feature Prioritization to justify why this feature goes first
- PRD Generator to write the spec
- Technical Handoff Brief to hand off to engineering
- Stakeholder Update to keep everyone aligned
Each step builds on the previous one. The context compounds.
Why prompt packs work for PMs
PMs operate across every part of the product org. They write docs, run meetings, analyze data, and plan strategy. A good prompt pack gives them a starting point for every one of these activities.
The prompts I built are specific enough to produce usable output but flexible enough to adapt to any product, any stage, any company size.
Get the pack
All 25 prompts are available as a single download in copy-paste format with detailed instructions. Pay what you want.
What PM workflows would you add next? I'm thinking about expanding to include product-led growth metrics and pricing strategy prompts.
I build free developer tools and write about productivity systems. Follow for more practical AI workflows.
