AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

Prompt pack4 steps11 prompts

Write a PRD / Product Spec

Use this when the bet is chosen and you need a spec people can build from. Problem and user first, then requirements and cuts, then how you will know it worked.

  1. 01Problem and user

  2. 02Requirements and scope

  3. 03Metrics and UX

  4. 04Review

Frequently asked questions

Do I need this after a design sprint?

If you are building, yes. The sprint shareout is evidence. The PRD is the contract.

We are still discovering the problem. Write a PRD anyway?

No. Run a research study or a sprint. A spec written to look busy will be rewritten after the first customer conversation.

How short can it be?

Short enough that engineering can build without Slack archaeology. Problem, who, in/out, success metric. If that fits in two pages, stop.