Instructions
A prototype spec is not a full product specification. It's the minimum blueprint needed to build something you can test with real users and get real signal from. The goal is to define exactly what you'll build first — and equally importantly, what you won't build yet — so that your first build effort produces maximum learning with minimum overhead.
The common mistake is writing a spec that's either too broad (trying to include every feature you want to build eventually) or too narrow (building a demo that can't really be tested by real users in a real workflow). A good prototype spec lands in the middle: scoped tightly enough that you can build it quickly, but realistic enough that the testing it enables is meaningful.
The prototype spec should address several specific things:...
