PRD prompt: a copy-paste prompt for a solid PRD

Here's a PRD prompt you can copy and use right now. Paste it into ChatGPT, Claude, or your coding agent, replace the parts in angle brackets, and you'll get back a real product requirements document — problem, goals, non-goals, user stories, requirements, and acceptance criteria — as clean markdown you can drop straight onto your board. It tells the model to ask you a few questions first, so the draft is grounded in your situation instead of guessing.

This is the primary prompt in our AI prompts library. For the full picture of what a PRD is and how to make one agents can execute, see the AI PRDs guide.

The prompt

You are a senior product manager. Help me write a product requirements
document (PRD) for the feature below. Write it in clear, plain language —
short sentences, no jargon, active voice.

Feature: <one or two sentences on what you want to build>
Who it's for: <the person who has this problem>
Context: <anything the model should know — the product, constraints, what
exists today, what's explicitly out of scope this version>

Before you write the PRD, ask me up to 5 clarifying questions that would
change what you draft. Wait for my answers.

Then write the PRD as a markdown file with exactly these sections:

# PRD: <feature name>
**Status:** Draft

## Problem
One paragraph. What's broken or missing today, and for whom. Use a concrete
example with a named person, not an abstraction.

## Goals
2–4 bullets. Each one an outcome, not a feature.

## Non-goals
What we are deliberately NOT doing this version. Be specific. This section
kills scope creep — don't skip it.

## Users
Who has this problem and what they're trying to do.

## User stories
Small, single-clause stories: "As a <role>, I want to <action> so that
<outcome>." One per line.

## Requirements
Numbered, testable statements of what the thing must do. Split "Must have"
from "Nice to have." Each requirement must be something a person or an agent
could verify pass/fail without asking a question.

## Acceptance criteria
Concrete, checkable statements that tell us the feature is done. Tie each
back to a requirement number.

## Open questions
Anything you're unsure about or that needs a decision from me.

Rules:
- Keep it to one to three pages. Short beats complete.
- Every requirement and acceptance criterion must be testable.
- Don't invent scope. If something's ambiguous, put it in Open questions.
- Return only the markdown, ready to paste into a file.

What you get back

Run it and the model returns a markdown PRD with the seven sections above, already filled in for your feature. Because you asked for markdown and named the headings, the output isn't chat prose — it's a document. You can paste it into a .md file, a doc tool, or a sfora post as-is.

The clarifying-questions step is the part that makes it good. Most PRD prompts guess at the details you didn't give and produce something generic. This one stops and asks, so the draft is about your feature — the real constraint, the real edge case, the thing that's actually out of scope. Answer honestly and the PRD comes back sharper.

How to run it in sfora

The prompt works in any AI chat, but the output is more useful when it lands as a file on your board. In sfora, everything is markdown, so a PRD is a first-class document, not an attachment.

Two ways to run it:

• Paste it into a post. Open a new post in sfora, drop in the prompt with your feature and context, and let the model draft the PRD right there. It's a real file the moment it's written — your team can read it, comment, and turn requirements into tasks.
• Hand it to your agent. Give the prompt to Claude Code, Cursor, or the sfora CLI over MCP. The agent drafts the PRD and writes it straight to your board as a markdown file — no copy-paste. Because agents are equal members of the same workspace, the same agent can then pick up the tasks and build against the acceptance criteria it just wrote.

That's the shift a generic PRD generator misses. The prompt doesn't just produce text you'll paste somewhere later — it produces a file that's already where the work happens.

Tips for a better draft

A prompt is only as good as the context you feed it. A few things that noticeably improve the output:

• Name a real person in the "who it's for" line. "A team admin rotating their API key" beats "users." The model writes a better problem statement when it has someone specific in mind.
• Fill in the "what's out of scope" part. This is the non-goals section doing its job before you even see the draft. It's the single biggest lever on how usable the result is.
• Answer the clarifying questions in full. Skipping them or answering "up to you" hands the scope decisions back to the model, which is exactly what you don't want.
• Then cut it. The draft will be thorough — probably too thorough. Read it, delete the requirements that don't matter for the first version, and keep the ones that do.

Where sfora fits

sfora is a workspace where humans and AI agents build products on the same team, and where everything — PRDs included — is a markdown file. Run this prompt in a sfora post and the PRD lands as a real document on your board. Hand it to your agent and the agent writes the file for you.

From there the loop is short: a person turns the requirements into tasks, and an agent picks those tasks up and builds against the acceptance criteria the prompt just wrote. The PRD stops being a document that describes the work and becomes the instruction the work runs on.

Next, break the PRD into work with the user story prompt, or write the technical detail with the product spec prompt. For the concepts behind all of this, read the AI PRDs guide, and see the docs for how agents read and write files in your workspace.