Draft a PRD from your team's notes
The decision lives across three chat threads and nobody has written it down. The agent drafts the PRD from your notes and lists what is still open.
Medium · 25 min · on an event
What you get
PRD draft, Google Docs — 6 sections Problem · Users · Scenarios · Requirements · Metrics · Risks Requirements go on their own sheet: R-04 Export orders to CSV <- ticket PM-212, Mar 14 R-05 Cap of 5,000 rows <- meeting notes, Mar 12 Open questions: 4. Among them, what happens when an export fails — the notes argued about it and never settled.
A sample on made-up data — your numbers will be your own.
Who it fits
- A week of discussion later, the agreements sit in notes, chats and tickets and no document exists.
- What matters is what the solution is missing: the open questions beat polished prose.
When it won't work
Almost no notes and the decision lives in one person's head — you get a plausible document about nothing.
How the agent does it
Gather the input
Link everything about the feature, including the threads where people disagreed — that is where the open questions come from. Attach your template too.
Run the build
The agent sorts notes into sections, puts a source on every requirement and keeps settled decisions apart from the ones still open.
Check for invention
Have the agent point out requirements with no source, and places where a hypothesis in the notes turned into a statement in the document.
What you set
Google Docs and Google Sheets. By hand: links to notes and tickets, your template if you have one, and the metrics you can actually measure.
What you'll need
Starter prompt
Copy the prompt or open it straight in a chat with the agent.
Build a draft PRD from [links to meeting notes, tickets, documents] and put it in Google Docs. Structure: the problem and who it hurts, what has already been tried, use cases, functional requirements, what is out of scope, success metrics, open questions. Mark every requirement with its source — a link to the note or a quote. If a decision was not made in the notes, do not make it for the team: move it into open questions as options and state who is responsible. Take only metrics we already know how to measure; for the rest write which data source is missing. Duplicate the requirements as a sheet in Google Sheets: number, wording, source, status.
Open in chatCheck the draft PRD. List: — requirements with no source link — where you took them from; — places where you picked one option out of several discussed, and why; — wordings that were a hypothesis in the notes but became a statement in the document; — metrics there is nothing to measure with given our current data collection; — contradictions between notes from different meetings that you smoothed over instead of showing; — what can be filled in from the existing notes and what requires a human decision.
A second prompt — the agent uses it to review its own work and show what's left for you.