How to Write Product Requirement Docs (PRDs) in the AI Era
a few of the things a vibe coded prototype doesn’t specify:
1. What is the **hypothesis** of the change?
2. How does this **fit within the overall strategy**?
3. Is it going to be **rolled out to everyone or A/B tested**?
4. What **constitutes passing metrics** to graduate the experiment?
5. What are **non-goals and potential side effects** that are worth accepting?