How long should a PRD for an AI builder be?

Between 400 and 800 words for a simple app. Longer is not better — if you are describing ten features in your first PRD, cut to five and move the rest to a v2 list. The goal is complete information per feature, not a comprehensive product vision.

Do I need a separate PRD for each AI builder I use?

No. Write one document and adapt the format. Paste it into Lovable or Bolt as the opening message. Save it as PRD.md in a Cursor project. Move the persistent context into CLAUDE.md if you switch to Claude Code. The substance stays the same; the format changes.

Can I use ChatGPT to write the PRD and then paste it into a builder?

Yes, but verify it covers the eight sections before you paste. ChatGPT tends to produce well-formatted documents that omit the data model and anti-goals — the two sections that most directly prevent expensive rewrites. Read the output critically before treating it as builder-ready.

Does the PRD replace a developer?

No. A PRD tells the builder what to build; it does not tell it what to do when something breaks, how to optimize a slow query, or when to push back on a dangerous implementation. Human review remains essential for anything going to production.

What is the difference between a PRD and a prompt pack?

A PRD is one structured document describing what to build. A prompt pack is a sequence of builder-specific prompts optimized for step-by-step construction — covering foundation setup, authentication, data layer, core features, and UI polish as separate messages. The PRD informs the prompt pack.

Should I include UI wireframes in the PRD?

Not for a first build. User flows described in plain text produce more consistent results than rough wireframes, which the builder may try to reproduce pixel-for-pixel rather than interpreting functionally. Once the core app works, you can use wireframes to refine the interface in a second pass.

How to Write a PRD for Lovable, Cursor, and Bolt

A PRD for AI builders is an instruction set, not a stakeholder document. Learn the eight sections that matter, how Lovable, Cursor, and Bolt consume context differently, and the mistakes that make builders guess wrong.