Skip to content

Write a product requirements doc with an agent

A PRD is one page on the problem, who it's for, what must be true when it ships and what you're not doing. Give an agent the facts and it drafts the structure in under 20 seconds.

8 min read
A product requirements doc drafted by Probe's agent in Work Studio, with Problem and Goals and non-goals sections

TL;DR

Collect the facts first (the problem, who has it, the deadline, what's out of scope). Open a Doc in Work Studio and ask Probe's agent to draft the PRD from only those facts, writing TBD where you haven't given a number. Apply its card, then fill in the TBDs with your team, share it with design and engineering, and keep it current as decisions change.

By the end of this guide you'll have a first PRD for a small feature, drafted by an agent from your facts and ready for your team to finish. The first draft takes under 20 seconds. Getting the facts straight beforehand takes 20 minutes, and it's the part that decides whether the PRD is any good.

Key takeaways

A PRD answers five questions: what problem, for whom, what must be true at launch, how you'll know it worked, and what you're not doing.
Write the facts down before you ask for a draft. The agent can't know them.
Ask the agent to use only your facts and write TBD where a number is missing.
Apply the draft, then fill every TBD with the people who own the answer.
Share it with design and engineering before anyone builds, and keep it current.

What is a product requirements document?

A product requirements document, or PRD, is the one page a team agrees on before building something. It says what problem the feature solves, who has the problem, what the feature must do, how you'll measure success, and what's out of scope. Atlassian describes it as one place that holds the project's specifics, goals, background, assumptions, user stories, design, open questions and "what we're not doing" (Atlassian (opens another site)).

It isn't a spec of every screen. Engineers and designers decide how; the PRD says what and why.

What goes in a PRD

For a small feature, these seven sections are enough:

SectionWhat it answers
ProblemWhat's broken today, in the user's words
Goals and non-goalsWhat this must achieve, and what it won't do
Who it's forThe people who have the problem
RequirementsMust-haves for launch, then nice-to-haves
How we'll measure successThe number that tells you it worked
Open questionsWhat nobody knows yet, and who will find out
TimelineThe date it has to be live, and why

The non-goals do more work than people expect. Writing "no payments in the first version" stops a week of debate later.

Bigger features add three more, all on Atlassian's list:

Assumptions: what you believe but haven't checked ("most clients book from a phone"). Each one is a risk to test.
User stories: one line per need, in the form "As a client, I want to see open slots, so I can book without emailing." They keep requirements tied to a person.
Design: a link to the mockups once design has them. The PRD doesn't draw screens; it points to them.

Background and strategic fit, a paragraph on why this matters now, helps when the PRD goes to people outside the team.

Product School's template also lists a few sections worth knowing, even if this guide's seven-section PRD skips them: change history (a log of what changed in the doc and when), messaging (how the feature is described to customers), Q&A (questions stakeholders raised and the answers), and other considerations (anything that doesn't fit elsewhere, like legal or support impact) (Product School (opens another site)). Add them when the feature is big enough that people outside the team will ask.

Before you start: write down the facts

Take 20 minutes and write the facts in plain sentences. These are the ones we used:

Clients of a five-person design studio can't book a call without three or four emails back and forth.
We want a page where they pick a 30-minute slot from our shared calendar.
They get a reminder the day before.
It must work on a phone.
No payments in the first version.
It has to be live by December 15, 2026.

Don't guess numbers you don't have, like how many clients book each month. Leave them out, and the draft will show where they're missing.

Step 1: Open a Doc

Open Work Studio, click New Paper and choose Doc. Name it after the feature; ours was "Booking page PRD".

A blank Doc open in Work Studio, ready to be named

Step 2: Ask the agent to draft it from your facts

Open the Probe AI chat beside your Doc and make sure it's in Agent mode. Put your facts and the sections in one request, and tell it what to do when a number is missing. This is ours:

Draft this Doc as a product requirements doc for a booking page. The facts: clients of a five-person design studio can't book a call without three or four emails back and forth; we want a page where they pick a 30-minute slot from our shared calendar and get a reminder the day before; it must work on a phone; no payments in the first version; we want it live by December 15, 2026. Sections: problem, goals and non-goals, who it's for, requirements as must-have and nice-to-have, how we'll measure success, open questions, and timeline. Use only these facts; where you need a number I haven't given, write "TBD".

Type or paste it into the chat box and press Enter to send it.

The last sentence is there so that a missing number comes back as TBD, which it did on our run.

The agent's card after drafting the PRD, with Apply and Reject buttons

Step 3: Read the card, then Apply

On our run the agent sent a card instead of typing into the Doc. Ours read Paper kind checked, confirming the doc matched its required structure, with Apply and Reject. It came back 18 seconds after we sent the request.

Click Apply. The chat confirmed Applied to Paper, and the draft is in your Doc. Read it for any TBD: those are the numbers you still owe it.

Step 4: Check what it did with your facts

The drafted PRD, with Problem, Goals and non-goals, and TBD marked where a number was missing

Read the draft against your list. Ours kept to the facts. The problem was our sentence. The goals were the three things we asked for. "Payments" sat under non-goals. All five must-haves came from our facts. And where we'd given nothing, it wrote TBD: under nice-to-haves, how we'll measure success, and open questions.

That's the draft you want. Every TBD is a decision, not a writing task.

Step 5: Turn the requirements into a table

Once you can see what's there, ask the agent to reshape a section. We asked:

Turn the requirements into a table with columns for requirement, must-have or nice-to-have, and why, and add an open question about time zones.
The agent's card proposing the three-column requirements table, with Apply and Reject buttons

Our card came back 42 seconds after we sent the request, headed Insert one block, with Apply and Reject. Ours also showed the warning "This Paper changed after the agent wrote this."

Click Apply: the requirements list becomes a three-column table, and a question about time zones is added to Open questions.

The requirements shown as a three-column table, with a time zone question added to Open questions

Step 6: Fill the TBDs with the people who own them

Go through each TBD and decide who answers it:

How we'll measure success: pick one number you can actually measure. For a booking page, that might be "share of calls booked without an email", before and after.
Nice-to-haves: ask design and engineering what would be cheap now and expensive later.
Open questions: write each as a question with an owner and a date. Time zones, cancellations and who gets notified are common ones for booking.

Type these yourself. It costs nothing, and these answers are the point of the document.

Step 7: Share it, get approval, keep it current

Product School's template walks through what happens next: get approval on the draft, then share it with design, engineering, the wider project team and the company (Product School (opens another site)). Click Share in the Doc's header to open its sharing options.

Atlassian names the most common failure: PRDs go stale. When a decision changes, change the PRD the same day, and note what changed and why at the bottom.

What it cost

Work Studio is on every Probe plan. The draft above cost 46 credits, and turning the requirements into a table cost another 86, 132 credits for both. On prices as of 7 November 2026, Free comes with 100 credits a month and Lite ($7.99 a month) with 800.

Mistakes that make a PRD useless

Writing how instead of what. "Use a calendar API" is engineering's call. "Clients see open slots from our calendar" is the requirement.
No non-goals. Without them, every meeting adds scope.
Numbers nobody can stand behind. In our view, a TBD beats a made-up target.
Writing it alone. A PRD nobody else has read isn't agreed. Ask design and engineering to comment before you call it done.
Letting it go stale. If the PRD says one thing and the team builds another, the PRD has stopped being useful. Update it when decisions change.

Questions people ask

What's the difference between a PRD and a spec?

A PRD says what to build and why. A technical spec says how engineering will build it. Write the PRD first.

How long should a PRD be?

One page for a small feature. If it runs much longer, it's probably more than one feature.

Can AI write a PRD for me?

It can draft the structure from your facts in under 20 seconds and show you which decisions are missing. The decisions themselves need the people who own them.

Who writes the PRD?

Usually the product manager, or whoever owns the feature. Design and engineering review it before building starts.

Do it on Probe

Open Work Studio, start a Doc, and ask the agent in Probe AI to draft your PRD from your facts, with TBD where a number is missing.

Was this helpful?