model product user risk: low
Product Manager PRD Generator
The prompt instructs the AI to acknowledge the request, respond as a product manager, and generate a PRD with headers including Subject, Introduction, Problem Statement, Goals and…
PROMPT
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.
INPUTS
- subject REQUIRED
-
The topic, feature, or development for which to write the PRD
e.g. user authentication feature
REQUIRED CONTEXT
- specific subject, feature or development
ROLES & RULES
Role assignments
- Please respond to me as a product manager.
- Acknowledge my following request.
- Do not write any PRD until I ask for one on a specific subject, feature or development.
EXPECTED OUTPUT
- Format
- markdown
- Schema
- markdown_sections · Subject, Introduction, Problem Statement, Goals and Objectives, User Stories, Technical requirements, Benefits, KPIs, Development Risks, Conclusion
- Constraints
-
- Acknowledge as product manager initially
- Use exact headers: Subject, Introduction, Problem Statement, Goals and Objectives, User Stories, Technical requirements, Benefits, KPIs, Development Risks, Conclusion
- Do not generate PRD until subject is provided
SUCCESS CRITERIA
- Acknowledge the request.
- Respond as a product manager.
- Write PRD with specified headers only when asked for a specific subject.
FAILURE MODES
- Writing a PRD without a specific subject being requested.
- Not using the exact specified headers.
- Failing to acknowledge the request.
CAVEATS
- Dependencies
-
- User must provide a specific subject, feature or development to trigger PRD writing.
- Missing context
-
- Guidelines or examples for content in each PRD section.
- Output format (e.g., Markdown).
- Target audience or product type assumptions.
- Ambiguities
-
- 'heders' is a typo for 'headers'.
- 'feature pr development' is unclear, likely 'feature or development'.
- Does not specify level of detail or length for each PRD section.
QUALITY
- OVERALL
- 0.70
- CLARITY
- 0.65
- SPECIFICITY
- 0.70
- REUSABILITY
- 0.80
- COMPLETENESS
- 0.70
IMPROVEMENT SUGGESTIONS
- Correct typos: change 'heders' to 'headers' and 'feature pr development' to 'feature or development'.
- Specify output format, e.g., 'Use Markdown with H2 headers for sections'.
- Add brief descriptions for each section, e.g., 'Problem Statement: Describe the user pain points'.
- Include a placeholder like 'When I provide {subject}, generate the PRD' for template use.
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR MODEL
- User Feedback Insights Synthesizermodelproduct
- Product Discovery Interview Facilitatormodelproduct
- Collaborative PRD Drafter for Product Featuresmodelproduct
- Apple-Level UI System Designermodelproduct
- Product PRD and Development Roadmap Plannermodelproduct
- Product Manager PRD Draftermodelproduct
- Product Image Selling Points Analyzermodelproduct
- Digital Visiting Card App Architectmodelproduct
- Water Balance Management Platform Designermodelproduct
- Non-Technical IT Help Assistantmodelcustomer_support