Vibe GuideClarify needs and scope
Answer one question at a time; undecided is a valid answer.
Why this milestone?
Explain unclear points before the tool builds the wrong thing.
Start here2 steps · Follow in order
0102Answer one question at a timeTo checkOpen this stepClose this step
01What do you need, and what should you keep?
Your idea.md and questions you have not decided yet.
idea.md contains your answers.
Which files should AI read and save in this step?
In your tool’s project chat, ask it to open the files below. If a file is missing, follow the link back to the step that creates it.
Ask AI to read these materials first: idea.md
Ask AI to save the result to: idea.md
Missing these materials? Return to the step that creates them →
02What will this step help you do?
Explain unclear points before the tool builds the wrong thing.
Understand it, then judge for yourself
What does this concept mean?
Answer one question at a time; undecided is a valid answer.
How would you decide in a different situation?
Could this unanswered question change the features needed in the first version?
See a reference answer
Clarify unknowns affecting users, required features, data, cost or delivery; defer nonessential details explicitly.
Answer in your own words; if unsure, compare the explanation above and check it against your own project.
03What exactly should you do in this step?
OpenClose
The project conversation with the idea draft
Send one action at a time: select and copy its prompt (⌘C on Mac, Ctrl+C on Windows), switch to your tool’s project chat, paste it, replace bracketed fields and send. Wait for the reply and check the stated result before continuing.
Ask the tool to read idea.md and find unclear parts.OpenClose
Suggested prompt:
Read idea.md and restate my goal in everyday language. Ask one question at a time about what is unclear. Do not code yet.
Afterwards, you should see: The tool restates the idea and asks an answerable question.
Answer the current question, or say undecided. Save once the first-version questions are clear.OpenClose
Suggested prompt:
Update idea.md with the answers I confirmed. List undecided items separately without deciding for me.
Afterwards, you should see: idea.md contains your answers.
Practice: personal journal (frontend + backend + database)
Use the same learning-journal project throughout this example. For your own project, compare applicable requirements without creating another project.
Answer one question at a time: user, public access, fields and retrieval. Start with one local user.
- What should you see after this step?
- Title, body and time are agreed; login and networked cross-device use are excluded.
- What should you do first if you get stuck?
- For shared online use, define identity and isolation before scope; do not expose the login-free practice.
04Not sure how? Follow each action
OpenClose
Ask the tool to read idea.md and find unclear parts.
- What should you see after this action?
- The tool restates the idea and asks an answerable question.
- What should you do if that result is missing?
- Ask for a simple example if it uses unfamiliar terms.
Answer the current question, or say undecided. Save once the first-version questions are clear.
- What should you see after this action?
- idea.md contains your answers.
- What should you do if that result is missing?
- Correct misunderstandings before saving.
05Words in this step
OpenClose
Requirement ↗
A specific need the project must satisfy.
Not “a good shop,” but “customers can see prices and order.”
Context ↗
The conversation, files, and background available for this turn.
Documents currently on the desk are readily available.
06How should you handle a problem here?
OpenClose
AI asks about unfamiliar technical terms
- Where should you look to understand the problem?
- Find the user-facing choice behind the technical question.
- Follow these steps to resolve the problem
- Reply: “Describe two real usage situations and their consequences so I can choose, without technical vocabulary.”
- Expected recovery
- The answer follows actual needs rather than guessed terminology.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am at “Answer one question at a time”. Expected: The draft separates confirmed facts from undecided items.. Actual screen/error: [add here]. Inspect existing files first. Give one reversible action at a time, its location, and expected result. Do not recreate the project or delete existing work.07Material for this step (fill or copy)
OpenClose
If you completed the individual prompts above, do not resend this full template. Use it to organize this step’s material when needed; replace bracketed fields, confirm and copy into the project chat.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
First check access to idea.md. If missing or inaccessible, identify the prerequisite and owner action, then stop rather than invent prior work.
Read idea.md and clarify only questions affecting version one. Restate users and goals, then ask one question at a time. Update confirmed and open items in idea.md only after the user answers. Preserve unknowns; do not decide for the user, implement or plan development. Indicate when scope can be agreed.Journal practice: fill or supplement this step
For this full-stack practice only: use this combined prompt, fill its fields and send it once instead of also sending the generic template. It does not authorize later steps.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
First check access to idea.md. If missing or inaccessible, identify the prerequisite and owner action, then stop rather than invent prior work.
Read idea.md and clarify only questions affecting version one. Restate users and goals, then ask one question at a time. Update confirmed and open items in idea.md only after the user answers. Preserve unknowns; do not decide for the user, implement or plan development. Indicate when scope can be agreed.
I selected the full-stack journal practice.
Clarify only unknowns affecting the local journal, distinguishing a second-browser check from Internet sharing.08Check this before continuing
The draft separates confirmed facts from undecided items.
09What should you do if the expected result is missing?
OpenClose
Ask for a simple example if it uses unfamiliar terms.
Compare with an example (illustration, not your result)
Reservation questions: who sets capacity, what counts as duplicate, and does cancellation free a place?
0202Choose only this version’s essentialsTo checkOpen this stepClose this step
01What do you need, and what should you keep?
The questions and answers you just confirmed.
The file distinguishes this version from later work.
Which files should AI read and save in this step?
In your tool’s project chat, ask it to open the files below. If a file is missing, follow the link back to the step that creates it.
Ask AI to read these materials first: idea.md
Ask AI to save the result to: docs/requirements.md
Missing these materials? Return to the step that creates them →
02What will this step help you do?
Decide what the first version must do and leave other ideas for later.
Understand it, then judge for yourself
What does this concept mean?
Version one is the useful part you will finish first, not every idea at once.
How would you decide in a different situation?
Can the core task finish without this feature?
See a reference answer
If removing it prevents the agreed goal, it is usually required; convenience improvements may be deferred by the owner.
Answer in your own words; if unsure, compare the explanation above and check it against your own project.
03What exactly should you do in this step?
OpenClose
The scope list from AI
Send one action at a time: select and copy its prompt (⌘C on Mac, Ctrl+C on Windows), switch to your tool’s project chat, paste it, replace bracketed fields and send. Wait for the reply and check the stated result before continuing.
Separate essential first-version work from later ideas.OpenClose
Suggested prompt:
Read idea.md and make two lists: needed in version one and later. Describe each as a user action. Show me first; do not code.
Afterwards, you should see: Both lists are understandable and contain no invented features.
Review each item, then save your decision.OpenClose
Suggested prompt:
Save the confirmed scope to docs/requirements.md, keeping later ideas and marking undecided items.
Afterwards, you should see: The file distinguishes this version from later work.
Practice: personal journal (frontend + backend + database)
Use the same learning-journal project throughout this example. For your own project, compare applicable requirements without creating another project.
Agree on creating records and listing history, with title, body and creation time.
- What should you see after this step?
- Create, list, failure feedback and retrieval have criteria.
- What should you do first if you get stuck?
- If accounts or cloud storage are proposed, ask whether local single-user use requires them.
04Not sure how? Follow each action
OpenClose
Separate essential first-version work from later ideas.
- What should you see after this action?
- Both lists are understandable and contain no invented features.
- What should you do if that result is missing?
- Reduce scope while keeping everything required for the core task.
Review each item, then save your decision.
- What should you see after this action?
- The file distinguishes this version from later work.
- What should you do if that result is missing?
- Fill important gaps before moving into development.
05Words in this step
OpenClose
MVP — Minimum viable product ↗
A usable product with enough features to test its core value.
Offer real reservations to learn whether people want the service.
Scope creep ↗
Adding requirements without adjusting the plan.
A table order grows into cabinets without a new budget.
06How should you handle a problem here?
OpenClose
Reducing scope left only a picture
- Where should you look to understand the problem?
- Can an input lead to a real result?
- Follow these steps to resolve the problem
- Keep the shortest complete flow. A journal can omit categories but must save and retrieve a record.
- Expected recovery
- One task can actually finish, rather than only displaying a page.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am at “Choose only this version’s essentials”. Expected: The list states actions and outcomes, not only “nice” or “easy”.. Actual screen/error: [add here]. Inspect existing files first. Give one reversible action at a time, its location, and expected result. Do not recreate the project or delete existing work.07Material for this step (fill or copy)
OpenClose
If you completed the individual prompts above, do not resend this full template. Use it to organize this step’s material when needed; replace bracketed fields, confirm and copy into the project chat.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
First check access to idea.md. If missing or inaccessible, identify the prerequisite and owner action, then stop rather than invent prior work.
Read idea.md and propose only version-one scope: required features, exclusions and observable passing criteria. Show it for user confirmation, then save the confirmed scope section in docs/requirements.md. List unknowns separately. Do not add features, code or choose technology.Journal practice: fill or supplement this step
For this full-stack practice only: use this combined prompt, fill its fields and send it once instead of also sending the generic template. It does not authorize later steps.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
First check access to idea.md. If missing or inaccessible, identify the prerequisite and owner action, then stop rather than invent prior work.
Read idea.md and propose only version-one scope: required features, exclusions and observable passing criteria. Show it for user confirmation, then save the confirmed scope section in docs/requirements.md. List unknowns separately. Do not add features, code or choose technology.
I selected the full-stack journal practice.
Number agreed scope: R1 input/list page; R2 backend validation and SQLite persistence; R3 error feedback, pending-submit protection and restart persistence.08Check this before continuing
The list states actions and outcomes, not only “nice” or “easy”.
09What should you do if the expected result is missing?
OpenClose
Reduce scope while keeping everything required for the core task.
Compare with an example (illustration, not your result)
R01 booking: never exceed capacity. R02 cancel: free a place. Later: payments.
Examples and reference
Now: write, save, view. Check: the same sentence remains after refresh. Excluded: accounts, sync, payment.
Words in this milestoneIn order of appearance; open for the full explanation
More troubleshooting references
Stuck? Start with what actually happens
2 situationsThese paths synthesize official docs and public reports, not frequency data. Check the symptom and verify the result.
AI asks questions full of jargon
Observed symptom: Database, authentication, and framework questions force guesses.
- What should you check first?
Separate business decisions from implementation choices that can wait.
- Then resolve
Ask one usage question at a time with two plain-language options and consequences. Let AI recommend technical choices with reasons and preserve unknowns.
- Verify the result
The owner can explain each decision, and no uncertain answer is recorded as confirmed.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: AI asks questions full of jargon.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Separate business decisions from implementation choices that can wait.
Proposed approach: Ask one usage question at a time with two plain-language options and consequences. Let AI recommend technical choices with reasons and preserve unknowns.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: The owner can explain each decision, and no uncertain answer is recorded as confirmed.
Report actual checks, unchecked items, and the next step.ReferencesLovable · Prompting best practices ↗
AI invents requirements
Observed symptom: Membership or payments appear despite never being requested.
- What should you check first?
Compare every item with idea.md; mark source, inference, and suggestion.
- Then resolve
Keep the original goal. Put additions in an open-question section until confirmed.
- Verify the result
Every confirmed requirement maps to source material or an explicit owner decision.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: AI invents requirements.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Compare every item with idea.md; mark source, inference, and suggestion.
Proposed approach: Keep the original goal. Put additions in an open-question section until confirmed.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: Every confirmed requirement maps to source material or an explicit owner decision.
Report actual checks, unchecked items, and the next step.ReferencesLovable · Prompting best practices ↗
Stuck? Start with what actually happens
2 situationsThese paths synthesize official docs and public reports, not frequency data. Check the symptom and verify the result.
The first version keeps growing
Observed symptom: Payments, membership, and admin arrive before one page works.
- What should you check first?
Identify what is essential to the main task.
- Then resolve
Sort features into required now, later, and excluded. Keep one complete input-to-result workflow.
- Verify the result
The current scope is bounded; new ideas go to a backlog.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: The first version keeps growing.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Identify what is essential to the main task.
Proposed approach: Sort features into required now, later, and excluded. Keep one complete input-to-result workflow.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: The current scope is bounded; new ideas go to a backlog.
Report actual checks, unchecked items, and the next step.ReferencesGitHub · Planning and tracking work ↗
A smaller scope becomes an empty shell
Observed symptom: The page looks good but submitting or saving is missing.
- What should you check first?
Check whether the reduced scope still produces one real result.
- Then resolve
Reduce roles, data types, and secondary entry points while keeping one verifiable workflow. Label mock data.
- Verify the result
Real operations and simulated steps are explicitly distinguished.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: A smaller scope becomes an empty shell.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Check whether the reduced scope still produces one real result.
Proposed approach: Reduce roles, data types, and secondary entry points while keeping one verifiable workflow. Label mock data.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: Real operations and simulated steps are explicitly distinguished.
Report actual checks, unchecked items, and the next step.ReferencesGitHub · Planning and tracking work ↗
References for this milestone
Open these when the question arises; they are not extra required actions.
- Which product form fits?
When the user entry point is undecided.
- How can AI stay on task?
When sending a new task, requesting an edit or reporting an error.
My project material and backups
Material stays in this browser, not in project files or AI chat. Chinese and English template drafts are separate; project selection and progress are shared. Do not enter passwords or API keys here.
Includes idea, progress, template drafts, personal checks and selection conditions, but not project code. Restore creates a new draft and preserves existing projects.
Download/import unavailable? Restore backup text
Draft and progress stay in this browser.
Complete the actions in order; expand the matching checks and remedies if you get stuck.