PRD

You might say

Help me spell out what I'm building for the AI: the problem it solves and what counts as done.

A product document that defines the user problem, scope, and success criteriaBefore a team builds one-click meeting-notes export, a PRD explains who needs it, what this release includes, and how the team will know it worked. It aligns product, design, and engineering without locking every technical detail.

Product Requirements Document

Turn one export request into a PRD the team can use

PRD · one-click meeting-notes exportv0.3 · In review

Section 1 of 6Background and problem

User interview · project manager

“After six meetings a week, just organizing the notes and forwarding them one by one takes 40 minutes.”

6+ meetingsmeetings per week

40 minutesper round of organizing and forwarding

3 peoplein-depth interviews

Fact · from 3 interviewsAssumption · recipients are the real readers

State who has what problem in which situation, and label what is fact versus assumption.

A PRD aligns decisions from background through acceptance. A technical proposal can link into it, but cannot make those decisions for it.

How a PRD aligns a team on one request

Start with the user problem and goal：Name the user, situation, and obstacle, then state the result the work should change.

Set the scope and non-goals：State required cases, constraints, and what this release will not address.

Agree on evidence：Use observable acceptance criteria or success signals, and keep assumptions and open questions with the request.

Quick checkChoose the best answer

A team is preparing a one-click meeting-notes export. Which set of content best forms the core of its PRD?

Target users and export pain points, in-scope and out-of-scope cases, success criteria, assumptions, and open questionsThe sequence, owners, and projected dates for every third-quarter initiativePredefine every database table, API field, and screen pixel without stating the user problem or validation criteria

You can say this to an AI Agent

Turn “one-click meeting-notes export” into a one-page PRD covering the target users, current problem, goal, scope, non-goals, and success criteria. Mark unsupported details as open questions instead of deciding the technical solution or drawing wireframes for the team; then check that every requirement can be verified.

Learn next

1User Flow→2MVP→