Prompt Library for Product Teams

I am building a feature called [FEATURE NAME] for my product [PRODUCT NAME]. The goal of this feature is [GOAL]. Draft a Product Requirements Document (PRD) including: 1) Problem Statement, 2) Target Audience, 3) Key Use Cases, 4) Scope and Out of Scope, and 5) Success Metrics.

I need to break down the feature [FEATURE NAME] into actionable user stories for the engineering team. Write 3-5 user stories using the 'As a [User Persona], I want to [Action], so that [Benefit]' format. For each story, provide 3 specific Acceptance Criteria (Given-When-Then format).

I have 3 potential features to build: 1) [FEATURE 1], 2) [FEATURE 2], 3) [FEATURE 3]. Evaluate each feature using the RICE framework (Reach, Impact, Confidence, Effort). Give me a projected RICE score for each and recommend which one we should build first based on maximizing ROI.

We are considering building a solution for [PROBLEM SPACE]. We are interviewing people who are currently using [COMPETITOR TOOL]. Draft a 15-minute user interview script. Focus on open-ended questions that uncover their current workflows, frustrations, and the 'job they are hiring the tool to do'.

Act as a seasoned Product Manager. Analyze my competitor: [COMPETITOR URL]. Identify their top 3 value propositions, their target market, and their pricing strategy. Most importantly, identify 2 potential weaknesses or 'feature gaps' in their product that we could exploit.

We just released version [VERSION NUMBER]. Here are the raw engineering tickets we shipped: [PASTE BULLET POINTS]. Rewrite these technical bullet points into an engaging, customer-facing 'What's New' release note. Focus on the benefits and value delivered, not the technical implementation.

We are introducing a complex new feature: [FEATURE DESCRIPTION]. Our current pricing model is a basic SaaS subscription ($X/month). Brainstorm 3 different ways to monetize this new feature: 1) Included in base tier to drive retention, 2) Add-on module, 3) Usage-based / Pay-as-you-go. List pros and cons for each.

We are about to start a 3-month development cycle to build [FEATURE]. Fast forward 6 months from now: the launch was a complete failure and nobody is using it. Conduct a 'pre-mortem' analysis. Give me the top 4 most likely reasons why it failed (e.g., poor UX, solved the wrong problem, performance issues) and how we can mitigate those risks right now.