This is a half-baked thought I want to develop further. Sharing it raw because I think the conversation is more interesting than the conclusion.
The provocation
A PRD is a document that says: here is what we want, here is why, here is how we'll know it worked. That's not far from a well-structured prompt.
What if your PRD wasn't a Notion doc but an executable file that could:
- Generate a starter prototype
- Generate the eval suite
- Generate the experiment plan
- Generate the launch announcement
Each of those is already possible in isolation. What's missing is the connective tissue — the idea that the artifact of intent is the source of truth, and everything else is downstream of it.
What I don't know
- Does this make PMs more powerful, or just create a new layer of bureaucracy?
- Who maintains the PRD-as-prompt as the product evolves?
- What does code review look like when half the codebase is generated from a doc?
If you've thought about this, I'd love to hear your take. The whole point of putting a half-baked idea on the internet is to find people with sharper takes.