Back to Prompts

AI Prompts for Delivery

52 prompts available for product managers.

PRD Generator

This prompt helps product managers create a clear and strategic Product Requirements Document (PRD) with guidance from a

6,927 uses

User Story

This prompt guides a Head of Product in crafting user stories that effectively translate user needs and business goals i

709 uses

Write Jira Issues

This prompt helps create a clear and concise Jira ticket for a product feature. Simply describe the feature’s purpose an

695 uses

v0.dev PRD Generator (Pro Ver.)

This prompt lets product leaders feed v0.dev a fully structured PRD and receive a multi-file, auto-modular Next.js 19 sc

483 uses

Discover the Best PM Tools

This prompt helps identify essential development and product management tools by generating a comprehensive list of soft

370 uses

Technical Concept Breakdown

This prompt helps explain technical concepts at a user’s desired level of understanding, whether they are a beginner, in

302 uses

Amazon-style 1-Pager

This prompt guides the creation of a strategic, execution-focused 1-Pager using Amazon’s silent reading format. It struc

226 uses

SRS(Software Requirements Specification) Generator

This prompt helps product managers write clear, actionable, and strategic Software Requirements Specifications (SRS). It

206 uses

One-Pager Generator

This prompt helps craft a concise, engaging, and impactful one-pager that effectively conveys your key message. Whether

201 uses

Key Product Metrics

This prompt helps define critical product metrics, aligning them with business objectives. It ensures a data-driven appr

108 uses

v0.dev PRD Generator (Simple Ver.)

This prompt guides product leaders through a structured, v0.dev-optimized template to create a share-ready Product Requi

97 uses

Develop a Growth Hacking Playbook

This prompt helps define growth hacking strategies using the AARRR framework (Acquisition, Activation, Retention, Revenu

90 uses

Design a Viral Product Growth Loop

This prompt helps structure viral loops and network effects to drive organic user acquisition and increase retention thr

75 uses

Design a fit-for-purpose delivery methodology for your team

Use this prompt when your team needs to move beyond rigid Scrum or Waterfall and design a customized delivery approach t

16 uses

Run a value-driven sprint retrospective with business impact scoring

Use this prompt to run a retrospective that goes beyond team process and explicitly connects sprint outcomes to business

14 uses

Diagnose why your product's shipping velocity is declining

Your team grew from 5 to 15 engineers but you're shipping fewer features per quarter than before. Standups feel pointles

10 uses

Build a technical debt negotiation case for your engineering team

Engineering keeps asking for 'tech debt sprints' but can't explain the business impact, and leadership keeps saying 'not

9 uses

Product Analytics Implementation Plan

Create a product analytics tracking plan that defines every event, property, and user attribute to instrument. Ensures y

9 uses

Incident Post-Mortem Template

Write a blameless post-mortem after a product incident. Structured to capture timeline, root cause, impact assessment, a

9 uses

Build a retention-focused onboarding optimization plan

Your signup-to-activation rate is low and users drop off before experiencing your product's core value. This dissects yo

8 uses

Product Brief Template

Create a concise product brief (1-2 pages) that aligns stakeholders before full PRD development. Faster than a PRD, perf

8 uses

Design a rigorous A/B testing program from scratch

Your team runs occasional experiments but has no systematic approach — tests overlap, sample sizes are guessed, and resu

8 uses

Create a product launch checklist with go-to-market sequencing

You're two weeks from a major feature launch and realize there's no coordinated plan across product, marketing, sales, a

8 uses

Sprint Planning Facilitator

Run an effective sprint planning session with your team. This prompt helps you prepare the sprint goal, select and estim

8 uses

Feature Specification Document

Write a detailed feature specification that engineering teams can immediately build from. Covers user flows, edge cases,

7 uses

QA Test Plan Generator

Generate a comprehensive QA test plan for a new feature or release. Covers functional testing, edge cases, regression sc

7 uses

Product Roadmap Generator

Create a strategic product roadmap organized by time horizon (Now / Next / Later) or quarterly themes. Includes prioriti

6 uses

Product Changelog & Release Notes Writer

Generate polished, user-friendly release notes and changelogs from raw commit logs, ticket lists, or sprint summaries. P

6 uses

Design a 90-day launch metric review

Your launch hit its week-1 activation target and everyone moved on. 90 days later nobody can say whether the feature mat

5 uses

Conduct a PM team meetings audit

Your PM team spends 18 hours a week in meetings and nobody can name what's shipping because of them. This runs an audit

5 uses

Run a Shape Up style 6-week cycle kickoff

Your 2-week sprints are producing shallow work and endless ceremonies. This runs the Shape Up kickoff — shaped pitch, ap

3 uses

Run a dependency mapping exercise across teams

Your roadmap says Q2 but three teams have silent dependencies on each other's work. This runs a dependency mapping exerc

3 uses

Run a Product Hunt launch playbook

You are launching on Product Hunt in 3-4 weeks and your previous attempt got 20 upvotes because you hit publish and hope

3 uses

Design a feature flag rollout plan with kill-switch

Ship-on-merge sounds brave until the first regression takes down prod. This designs a flag-gated rollout — cohort-by-coh

2 uses

Run a DRICE prioritization session with diligence scoring

RICE gave you a ranked list — and three of your top bets flopped last quarter because nobody pressure-tested the reach o

2 uses

Design a one-team-one-roadmap consolidation

Sales has a roadmap, CS has a roadmap, marketing has a roadmap, product has a roadmap, and none of them match. This runs

2 uses

Build a scope creep defense document

You kicked off a 6-week project and 4 weeks in it is now a 10-week project. Every added item had a good reason. This pro

2 uses

Design an engineering excellence review for PMs

You're the PM and you can't tell whether your engineering team is healthy or coasting. This designs an engineering excel

2 uses

Design a go/no-go review template

Leadership needs a clear go/no-go decision and your 40-slide status deck buries it. This produces a 2-page template that

2 uses

Build a technical debt triage framework

Your team wants a "tech debt sprint" and leadership says "ship features." Both are wrong. This builds a triage framework

2 uses

Run a pre-launch readiness review checklist

Launch day is 5 days out and the team is confident — which is when things break. This runs a pre-launch review across pr

2 uses

Design a shipping velocity diagnosis using cycle time

Leadership says "we're slow" and the team says "we're shipping plenty." This cuts through the debate using cycle time —

2 uses

Conduct a feature sunset plan

A feature has 0.5% usage and costs 2 engineers/quarter to maintain. Support keeps getting tickets. The team keeps saying

1 uses

Build a cross-team kickoff doc for shared infrastructure

You are building shared infrastructure that 4 teams will consume and three of them weren't at kickoff. This produces a k

1 uses

Conduct a merge-conflict root cause analysis

Your team is spending hours per week on merge conflicts and everyone blames the other team. This runs a structured analy

1 uses

Run a beta customer recruitment and success plan

You need 10-20 real customers on a beta in 4 weeks and your CS team is fully booked. This builds the recruitment spec, s

1 uses

Design a bug SLA tiering system

Every bug feels urgent and engineering is reacting to the last Slack message. This designs a bug SLA tiering system — P0

1 uses

Run a rolling roadmap quarterly re-plan

Your annual roadmap is dead by quarter two. This runs a quarterly re-plan that keeps the strategy pillars fixed but re-s

1 uses

Conduct a release retrospective with metric check-ins

Two weeks after launch and the team has moved on — but the launch metrics are only now maturing. This schedules structur

1 uses

Conduct a blameless incident post-mortem

Your last incident post-mortem turned into a name-and-shame and nobody wants to run the next one. This walks through a b

1 uses

Build a sprint retrospective with business-impact scoring

Your retros produce the same 3 action items every 2 weeks and nothing compounds. This restructures the retro around busi

0 uses

Build a sprint planning facilitator agenda

Your sprint planning runs 90 minutes, everyone is checked out by minute 30, and the output is a backlog nobody believes.

0 uses