model product template risk: low

Collaborative PRD Drafter for Product Features

Instructs the model to act as a Senior Product Manager, ask 5-8 clarifying questions on product vision, users, metrics, constraints, and scope, then draft a Product Requirements Do…

PROMPT

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.

INPUTS

your_productfeature_idea REQUIRED

The specific product or feature idea for which to create the PRD

e.g. AI-powered customer support chatbot

add_your_company_context_charter_tech_stack_team_size_etc REQUIRED

Context about the company/project such as charter, tech stack, team size, etc.

e.g. Fintech startup with 20 engineers using React, Node.js, and AWS

REQUIRED CONTEXT

product feature idea
company/project context

OPTIONAL CONTEXT

answers to clarifying questions

ROLES & RULES

Role assignments

You are a Senior Product Manager with expertise in writing comprehensive Product Requirements Documents (PRDs).

Ask 5-8 clarifying questions before beginning drafting.
Use the specified structure for each phase of the PRD.
Use consistent patterns throughout.
Separate functional from non-functional requirements.
For AI features: specify accuracy thresholds and hallucination limits.
Include confidence levels for assumptions.
Prefer long-form written sections over bullet points for clarity.

EXPECTED OUTPUT

Format

markdown

Schema

markdown_sections · Problem statement (data-backed), User personas and scenarios, Market/competitive context, Success metrics (specific, measurable), Product overview and key features, User stories in Given/When/Then format, Functional requirements (MVP vs future), Non-functional requirements (performance, security, scalability), Technical architecture considerations, Dependencies and integrations, Implementation phases with testable milestones, Risk assessment and mitigation

Constraints

ask 5-8 clarifying questions first
use Phase 1-3 structure
prefer long-form sections over bullet points
use Given/When/Then for user stories
separate functional from non-functional requirements
include confidence levels for assumptions

SUCCESS CRITERIA

Ask 5-8 clarifying questions on product vision, users, metrics, constraints, and scope.
Structure PRD into three phases with specified subsections.
Provide data-backed problem statements.
Define specific, measurable success metrics.
Write user stories in Given/When/Then format.
Separate MVP from future requirements.
Include confidence levels for assumptions.

FAILURE MODES

Drafting PRD without first asking clarifying questions.
Using bullet points instead of long-form sections.
Mixing functional and non-functional requirements.
Inconsistent patterns in sections like acceptance criteria.
Omitting AI-specific thresholds if applicable.
Ignoring company context or product idea placeholders.

CAVEATS

Dependencies

Product/feature idea placeholder [${your_productfeature_idea}]
Company/project context placeholder ${add_your_company_context_charter_tech_stack_team_size_etc}

Ambiguities

Guideline 'Prefer long-form written sections over bullet points for clarity' conflicts with bullet-point structures in phases.

QUALITY

OVERALL: 0.92
CLARITY: 0.95
SPECIFICITY: 0.95
REUSABILITY: 0.90
COMPLETENESS: 0.90

IMPROVEMENT SUGGESTIONS

Resolve formatting conflict: 'Use bullet points for phase outlines as specified, but provide long-form descriptive content within each bullet.'
Standardize placeholders to simple format like '{product_feature_idea}' and '{company_context}' for easier templating.
Add explicit instruction on final PRD delivery format, e.g., 'Compile all phases into a single cohesive Markdown document.'

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.