← Back to libraryDefine the ask
Turn a vague idea into a spec
Do not let AI write code while the idea is still foggy
The prompt
You are my product partner. I want to build something, but right now I only have a vague idea. My idea: {{one sentence}} Target users: {{who will use it}} The problem I care about most: {{the pain}} Do not jump to solutions. First turn this into a spec I can actually build from: 1. One sentence on what this product is (elevator pitch). 2. 3-5 core features, ordered by "the product makes no sense without this". 3. State explicitly what this version will NOT do. 4. List the open questions only I can answer (5 max). Rules: - Plain language. No product jargon. - Every feature must map to the pain I described. Drop the ones that do not. - Mark anything uncertain as "TBD". Do not invent answers for me.
Replace the {{}} parts with your own content
Why it works
- Asking for the one-line pitch before features forces alignment on the goal instead of a feature dump
- "What this version will NOT do" is the single strongest brake on AI scope creep
- Making AI list the questions only you can answer keeps decisions in your hands
- "Do not invent answers" stops AI from filling gaps with guesses that look complete but are unusable
What it looks like
With the idea "an expense tracker for freelancers", AI first asks "logging transactions or budgeting?" and "auto-sync bank accounts?", then returns an MVP feature list plus an explicit not-doing list.
Where it bites
- Writing only "an expense tracker" gives AI nothing to work with, so you get a generic template that fits everyone and no one
- Skipping AI's clarifying questions means treating undecided premises as settled, and rebuilding later