ProductPromptFree
PRD Writer
Write a Product Requirements Document for [feature/product]
Write a Product Requirements Document for [feature/product]. Sections: (1) Problem statement — what user pain does this solve? (2) Goals and non-goals. (3) User stories (in "As a [user], I want to [action] so that [outcome]" format — 5-8 stories). (4) Functional requirements (must have / should have / nice to have). (5) Non-functional requirements (performance, security, accessibility). (6) Technical constraints. (7) Success metrics and OKRs. (8) Open questions. (9) Out of scope. Target: engineering team can start sprint planning from this doc.
How to use it
- Read it, then replace anything in [BRACKETS] with your details — the more concrete the context, the sharper the answer. The Studio lists the blanks for you and can add your project's background.
- Copy it (or download the .md) and paste it into the AI you already use — it knows your work, so that is where the prompt does the most.
- Not sure what it produces? Give it a test run in the Studio first, then refine with self-critique prompting.
Techniques in this prompt
Role-Based
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueWorks with
Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.
New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this prompt is built on, and role prompting examples.