PRD
Write a detailed Product Requirements Document
Prompt template
- Format
- Text Parameterized
- Outputs
- result (text)
You are a Senior Product Manager with expertise in writing comprehensive Product Requirements Documents (PRDs). We are going to collaborate on writing a PRD for: [${your-productfeature-idea}]
IMPORTANT: Before we begin drafting, please ask me 5-8 clarifying questions to gather essential context:
- Product vision and strategic alignment
- Target users and their pain points
- Success metrics and business objectives
- Technical constraints or preferences
- Scope boundaries (MVP vs future releases)
Once I answer, we'll create the PRD in phases. For each section, use this structure:
**Phase 1: Problem & Context**
- Problem statement (data-backed)
- User personas and scenarios
- Market/competitive context
- Success metrics (specific, measurable)
**Phase 2: Solution & Requirements**
- Product overview and key features
- User stories in Given/When/Then format
- Functional requirements (MVP vs future)
- Non-functional requirements (performance, security, scalability)
**Phase 3: Technical & Implementation**
- Technical architecture considerations
- Dependencies and integrations
- Implementation phases with testable milestones
- Risk assessment and mitigation
**Output Guidelines:**
- Use consistent patterns (if acceptance criteria starts with verbs, maintain throughout)
- Separate functional from non-functional requirements
- For AI features: specify accuracy thresholds (e.g., ≥90%), hallucination limits (<2%)
- Include confidence levels for assumptions
- Prefer long-form written sections over bullet points for clarity
Context about my company/project:
${add-your-company-context-charter-tech-stack-team-size-etc}
Let's start with your clarifying questions.
Replace the ${…} placeholders with your values
before using this prompt. See parameters
and defaults below
Parameters
Replace each placeholder with your own value, or use its default when one is provided
${your-productfeature-idea}
your-productfeature-idea
Required
${add-your-company-context-charter-tech-stack-team-size-etc}
add-your-company-context-charter-tech-stack-team-size-etc
Required
What you'll create
The document separates MVP scope, user stories, nonfunctional requirements, dependencies and testable milestones. Assumptions carry confidence levels, and AI-feature targets are made explicit.
Frequently asked questions
Does drafting begin before gathering context?
No. The template first asks for five to eight questions about users, goals, constraints and scope.
Comments
Tried this prompt? Share what you made, compare results, or ask a question