---
type: method
slug: product-requirements-document
title: "Write a product requirements document (PRD)"
category: "Product Development"
subcategory: "Definition & specs"
level: intermediate
source: https://deepstoryresearch.com/method/product-requirements-document
publisher: Deepstory Research
---

> **How to use this file:** attach it to ChatGPT, Claude, Gemini or Copilot (or paste the prompt section), replace every [PLACEHOLDER] with your details, and add any data or Deepstory evidence files the method needs.

## When to use this method
- Handing a feature to design and engineering.

## Prompt

# Write a product requirements document (PRD)
Method by Deepstory Research: deepstoryresearch.com/method/product-requirements-document

You are a senior product manager. Follow the method below step by step. Goal: A PRD with problem, goals, non-goals, users, requirements, UX notes, metrics and open questions.

## My inputs
- Feature idea: [FEATURE_IDEA]  (example: saved searches with alerts)
- User problem and evidence: [USER_PROBLEM_AND_EVIDENCE]  (example: users re-run the same search daily)
- Constraints: [CONSTRAINTS]  (example: must ship in 6 weeks)

Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source.

## Steps to follow
1. State the problem and evidence.
2. Set goals and explicit non-goals.
3. Describe users and use cases.
4. Write functional requirements with priority (must/should/could).
5. List non-functional requirements (performance, privacy, accessibility).
6. Define success metrics and launch criteria.
7. List risks and open questions.

## Deliver the output in this structure
- Problem
- Goals / non-goals
- Users & use cases
- Requirements table
- Non-functional requirements
- Metrics
- Risks & open questions

## Quality rules
- Requirements are testable.
- Non-goals are listed to prevent scope creep.
- Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION.
- If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED].
- End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.

## Evidence you can attach
- E-Commerce Share of US Retail: https://deepstoryresearch.com/data/us-ecommerce-share (AI context file: https://deepstoryresearch.com/context/us-ecommerce-share.md)
- Six-Economy Macro Baseline: https://deepstoryresearch.com/data/global-macro-baseline (AI context file: https://deepstoryresearch.com/context/global-macro-baseline.md)

---
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment matters need a qualified professional.