Product Management
Never miss a step when launching
Create a comprehensive launch checklist for: **Product:** [what's launching] **Launch Type:** [new product/feature/major update] **Launch Date:** [when] **Audience:** [who it's for] Generate checklists for: **T-4 Weeks:** - Marketing preparation - Documentation & help content - Internal training **T-2 Weeks:** - Final testing & QA - Stakeholder sign-offs - Rollback plan **T-1 Week:** - Soft launch / beta - Monitor & fix critical issues - Press/partner coordination **Launch Day:** - Go/no-go decision criteria - Announcement sequence - War room setup **Post-Launch:** - Success metrics tracking - Customer feedback loops - Iteration priorities Include owners and due dates placeholders.
Create comprehensive PRDs quickly
You are a product leader creating a Product Requirements Document for: Feature/Product: [WHAT ARE YOU BUILDING] Problem Statement: [WHAT PROBLEM DOES IT SOLVE] Target Users: [WHO IS THIS FOR] Include: 1. Executive Summary 2. Problem & Opportunity 3. Goals & Success Metrics 4. User Personas 5. Feature Requirements (prioritized) 6. Technical Considerations 7. Timeline & Milestones 8. Risks & Mitigations
Keep stakeholders informed efficiently
Write a stakeholder update email for: **Project/Product:** [name] **Audience:** [executives/board/cross-functional] **Update Period:** [weekly/monthly/quarterly] **Current Status:** [on track/at risk/blocked] Structure the update as: **TL;DR** (3 bullet points max) **Progress Highlights** - Key milestones hit - Metrics movement **Challenges & Mitigations** - What's at risk - What we're doing about it **Decisions Needed** - Clear asks with context - Deadline for decisions **Next Week Focus** - Top 3 priorities **Appendix** (optional) - Detailed metrics - Timeline updates Tone: Confident but honest. No corporate fluff.
Break features into actionable, well-defined stories
Break down this feature into well-structured user stories: **Feature:** [describe the feature] **Context:** [product area, user type] **Business Goal:** [why we're building this] For each user story: 1. **Story:** As a [user], I want [goal], so that [benefit] 2. **Acceptance Criteria:** Given/When/Then format (3-5 criteria) 3. **Edge Cases:** What could go wrong 4. **Dependencies:** What needs to exist first 5. **Story Points:** Rough estimate (1/2/3/5/8) 6. **Notes:** Technical considerations, open questions Organize stories by: - MVP (must-have for launch) - V1.1 (fast-follow improvements) - Future (nice-to-have) Include a dependency diagram description.
Write clear, actionable user stories
You are a senior product manager. Write detailed user stories for: Feature: [DESCRIBE THE FEATURE] Product: [WHAT PRODUCT IS THIS FOR] Users: [WHO WILL USE THIS] For each user story provide: 1. User Story: As a [user type], I want [action] so that [benefit] 2. Acceptance Criteria: Specific, testable conditions 3. Edge Cases: What could go wrong? 4. Dependencies: What needs to exist first? 5. Story Points Estimate: T-shirt size with reasoning