Product Manager
What it does
Bridge the gap between a raw feature idea and a technical execution plan by generating comprehensive Product Requirements Documents (PRDs). This skill streamlines the documentation process, ensuring you don't miss critical sections like KPI definitions, technical constraints, or risk assessments. It is particularly useful during the discovery and planning phases of a sprint when you need to align stakeholders, designers, and engineers on exactly what is being built and why. Instead of staring at a blank page, you get a structured framework that forces clarity on the problem statement and user value before a single line of code is written.Use cases
- New Feature Launch: Drafting a detailed spec for a new user-facing tool to ensure the engineering team understands the acceptance criteria.
- MVP Definition: Narrowing down a broad product vision into a lean set of user stories and goals for an initial release.
- Stakeholder Alignment: Creating a formal document to present to executives to justify the business benefits and expected KPIs of a proposed change.
- Technical Handoff: Providing developers with a clear list of technical requirements and potential development risks to avoid mid-sprint blockers.
How to use
Initialize the AI by pasting the prompt below. Once the AI acknowledges the role, simply send the subject, feature name, or a brief description of the development task you are working on.text
Please acknowledge my following request. Please respond to me as a product manager. I will ask for subject, and you will help me writing a PRD for it with these heders: Subject, Introduction, Problem Statement, Goals and Objectives, User Stories, Technical requirements, Benefits, KPIs, Development Risks, Conclusion. Do not write any PRD until I ask for one on a specific subject, feature pr development.Tips
- Provide Context: When you provide the subject, include 2-3 sentences about your target audience and the current pain point to make the "Problem Statement" and "User Stories" more accurate.
- Iterate by Section: If a specific section (like Technical Requirements) is too generic, ask the AI to "expand the Technical Requirements section with specific API considerations" after the initial PRD is generated.
- Define the Persona: Tell the AI who the "User Stories" are for (e.g., "the admin user" or "the first-time visitor") to get more precise acceptance criteria.
- Ask for Alternatives: Once the PRD is done, ask the AI to suggest one alternative approach to achieving the same goal to stress-test your logic.
Notes
- Domain Knowledge: The AI may generate generic technical requirements; you should always review these with your lead engineer to ensure they align with your actual tech stack.
- KPI Validity: Suggested KPIs are based on industry standards and may need to be adjusted to fit your specific business metrics and tracking capabilities.