Write the PRD before you write a single prompt
The fastest way to build with AI is to slow down for one hour first. Here’s the one document that changes everything.
Samuel Audu4 Nov 2026·2 min read
Vibe Coding
Most people start vibe coding by typing their idea into an AI tool and hoping. It works for ten minutes. Then the AI forgets what you agreed, rewrites a screen you liked, and you spend the evening explaining your app again.
The fix isn’t a better prompt. It’s a document the AI can read every single session: a PRD, or product requirements document.
What goes in a PRD
Keep it short. One page is better than ten. Mine always covers:
- A one-line pitch: what it is and who it’s for
- The problems it solves, in the user’s words
- The core pillars: the three or four things it must do well
- Where it launches and how it’s priced
- What’s out of scope for now
Treat it like a contract
The PRD is the agreement between you and the AI. When a decision changes, you change the document first, then ask the AI to build. Version it (v0.1, v0.2) so you can see how your thinking moved.
Pair it with a feature list
Next to the PRD, keep a simple FEATURES.md. Tag every feature MVP (ships at launch), 1.1 (first update) or 2.0 (later), and mark what’s already built. It’s the cheapest scope-creep protection you’ll ever get.
“The docs are the AI’s memory between sessions. Write them first, then the code.”
Written by
Samuel Audu
I build real products with AI and teach the process in a live class. More about me