Skip to main content
Prompts Product Requirements Document Drafter

general user product assistant_example risk: low

Product Requirements Document Drafter

Acknowledges request to draft a comprehensive Product Requirements Document (PRD) and prepares to assist once a specific subject, feature, or initiative is provided. Generates the…

PROMPT 

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.

REQUIRED CONTEXT

  • specific subject, feature, or development initiative

ROLES & RULES

  1. Do not initiate PRD until a clear topic is provided.
  2. Use structured format including Subject, Introduction, Problem Statement, Goals and Objectives, User Stories, Technical Requirements, Benefits, KPIs, Development Risks, and Conclusion.

EXPECTED OUTPUT

Format
structured_report
Schema
markdown_sections · Subject, Introduction, Problem Statement, Goals and Objectives, User Stories, Technical Requirements, Benefits, KPIs, Development Risks, Conclusion
Constraints
  • use structured format with sections: Subject, Introduction, Problem Statement, Goals and Objectives, User Stories, Technical Requirements, Benefits, KPIs, Development Risks, and Conclusion

SUCCESS CRITERIA

  • Draft comprehensive Product Requirements Document (PRD)
  • Include all specified sections in structured format

FAILURE MODES

  • Initiating PRD without specific subject
  • Omitting required sections
  • Failing to wait for user-provided topic

CAVEATS

Dependencies
  • Specific subject, feature, or development initiative from user
Missing context
  • Detailed guidelines or examples for content in each PRD section
  • Desired depth, length, or tone for the PRD
  • Target audience for the PRD

QUALITY

OVERALL
0.80
CLARITY
0.95
SPECIFICITY
0.90
REUSABILITY
0.65
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Add brief descriptions of expected content for each section, e.g., 'Problem Statement: Clearly articulate the user pain points and market gap.'
  • Introduce a placeholder like [TOPIC] to make it a reusable template: 'Draft a PRD for [TOPIC] using the following structure...'
  • Specify success criteria, such as 'Ensure the PRD is actionable and prioritized.'

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 GENERAL USER