# Writing a PRD

**Categories:** Using AI

---

A Product Requirements Document (PRD) says what to build and why, not how. Retain writes one from the interviews, planning meetings and email you have already captured, quotes the people who said it, and marks what the record does not support. This page covers how to ask for one, what it contains, and how to change it.



### Choose a PRD yourself



Retain never proposes a PRD on its own. You choose it, in one of two places.



* **On a plan step.** A plan is the list of documents Retain proposes from a meeting or a Thread, and each item is a step. Open a step and set **Type** to **PRD**. The menu lists **Technical Design** and **PRD** side by side, and picking any other type takes the PRD choice off. For where plans come from, see [From a meeting to a design doc](https://retainapp.ai/help/article/from-a-meeting-to-a-design-doc).
* **On a new empty document.** On the Mac, choose **Document** in Create New, open the **Kind** menu under the title and pick **Product Requirements Document**. Type what it should cover and select **Write**. On iPhone, the **Kind** menu is on the write bar beside the model picker. **Automatic** leaves the document to the document chat.

The finished PRD opens as a new document, and the empty one is removed.



### What Retain writes



A PRD runs about 800 to 1,500 words, in this order:



* **Problem.** Who has it and what it costs them today.
* **Users and their jobs.** Each kind of user and what they are trying to get done.
* **Goals and non-goals.** What success changes for the user, and what this leaves out.
* **Requirements.** Numbered, each marked **Must** or **Should**, each with a line saying how to tell it is met.
* **Success metrics.** How the outcome is measured, with the current value when the sources give one.
* **Scope and phasing.** What ships first, what waits, and why.
* **Open questions.** What is undecided and who can decide it.
* **Evidence.** What users and stakeholders said, word for word, with the speaker, the time and the meeting or email it came from.

Every requirement traces to the problem or to the evidence.



### What makes a good source



Retain reads up to 20 sources for one PRD. The strongest are:



* **User interviews** recorded with the **User interview** meeting type, which keeps the interviewee's problems, workarounds and quotes in their own words, with a time for each quote. See [Meeting types](https://retainapp.ai/help/article/meeting-types).
* **Planning meetings** where the team said what it wants and what it will not do.
* **Email** with stakeholders or customers.

Without these a PRD has little to quote, so capture first; see [How to capture meetings with Retain](https://retainapp.ai/help/article/retain-app-how-to-capture-meetings-with-retain). On a plan step, **Draws on** lists the sources the PRD will read.



### Assumptions are marked



Anything the sources do not support, such as a market size or a deadline nobody gave, is marked as an assumption instead of stated as fact. Read those first and confirm each before you share the document.



### Revise it



Show the AI chat beside the document and say what to change, such as "split the second Must into two" or "move billing to a later phase".



### Change a document's kind



A written document can become a PRD. Open it and use its **Kind** menu to pick **Product Requirements Document**. The label changes and the text stays. A line then reads "Written as Technical Design Document" with **Regenerate as Product Requirements Document** beside it. Select that and Retain writes a new PRD from the document's text, leaving the original in place. Nothing is rewritten until you select it.



### What comes next



When engineers pick up a PRD, the work becomes a [build packet](https://retainapp.ai/help/article/build-packets) you can follow in [the Work list](https://retainapp.ai/help/article/the-work-list). [Threads and what's owed](https://retainapp.ai/help/article/threads-and-whats-owed) keeps track of who owes the next step.
