Pin down requirements before asking AI to build
Turns every gap into a question instead of a guess, and ends with a request you can paste.
| Category | Development › Vibe coding |
|---|---|
| Tags | Question generationDraftingDeveloper |
Organize my requirements before I ask an AI to build this. ***Do not write code yet.*** Organize: 1. What is being built — one sentence 2. What the user does — screens and steps, in order 3. Data — what is stored and where 4. **What is out of scope this time** 5. Technical constraints — decided on, ruled out 6. **Definition of done** — what has to work for this to be finished Rules: - ***Anything missing from my description comes back as a question. Do not fill it with a guess.*** **A guess filled in here is the reason you rewrite it later.** - **Ask these specifically:** does it need login, is data shared between users, what happens when something fails. - If I say "you decide", **give me options and let me pick.** Do not decide for me. - When it is organized, **produce a request I can copy and paste, then stop.**
After pasting, fill in the fields at the bottom (What I want to build · My experience · Tools and environment)
What this prompt does
Vibe-coding fails on the assumptions filled in silently at the start. This surfaces them as questions while changing them is still cheap.
More in this category
| AI builder | |
| AI-Powered Personal Compliment & Coaching Engine | |
| Anime | |
| Business Engineer Dashboard Creator | |
| Dating Profile Optimization Suite |