Project Manager
What it does
Streamline the creation of Product Requirements Documents (PRDs) by enforcing a rigorous, industry-standard structure. Instead of getting fragmented lists of features, you get a comprehensive blueprint that bridges the gap between business goals and technical execution. This is particularly useful during the discovery phase of a sprint or when transitioning a rough idea into a formal specification for engineering teams. By forcing a focus on problem statements, user stories, and KPIs, it ensures that every technical requirement is tied to a measurable business outcome, reducing scope creep and misalignment between stakeholders.Use cases
- New Feature Launch: Drafting a detailed spec for a new module to ensure developers understand the "why" before the "how."
- MVP Definition: Narrowing down a broad product vision into a concrete set of initial requirements and success metrics.
- Technical Handover: Converting a client's vague request into a structured document that can be used for estimation and sprint planning.
- Legacy System Overhaul: Documenting the current problems of an old feature to justify the technical requirements for a rewrite.
How to use
Paste the prompt below into your AI assistant. Once the AI acknowledges the role, provide it with a brief description of your feature, a project title, or a rough set of notes.text
I acknowledge your request and am prepared to support you in drafting a comprehensive Product Requirements Document (PRD). Once you share a specific subject, feature, or development initiative, I will assist in developing the PRD using a structured format that includes: Subject, Introduction, Problem Statement, Goals and Objectives, User Stories, Technical Requirements, Benefits, KPIs, Development Risks, and Conclusion. Until a clear topic is provided, no PRD will be initiated. Please let me know the subject you'd like to proceed with, and I’ll take it from there.Tips
- Provide Context First: The more context you give in your initial subject (e.g., "User authentication using OAuth2 for a healthcare app"), the more precise the Technical Requirements and Risks sections will be.
- Iterate Section by Section: If the project is massive, ask the AI to draft the "Problem Statement" and "Goals" first. Review them, then tell it to proceed with the "User Stories."
- Challenge the KPIs: After the PRD is generated, ask the AI to suggest alternative KPIs if the initial ones feel too vague or untrackable.
- Feed it User Feedback: Paste actual customer complaints or interview transcripts when describing the subject to make the "Problem Statement" more authentic.
Notes
- Lack of Domain Expertise: The AI may suggest generic technical requirements; always have a lead engineer review the "Technical Requirements" section for architectural feasibility.
- Scope Blindness: While it identifies risks, it cannot know your team's specific velocity or internal technical debt, so you'll need to manually adjust the "Development Risks."