> For the complete documentation index, see [llms.txt](https://docs.genvibe.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.genvibe.pro/features/plan-mode.md).

# Plan mode

By default, GenVibe builds as soon as you send a prompt. **Plan mode** adds a step before that: GenVibe thinks *with* you first — asking a few quick questions and laying out a plan — and only starts building once you approve it.

It's great for bigger or fuzzier ideas where you want to steer the direction before a single file is written.

## Build vs Plan

Next to the send button there's a mode dropdown:

* **Build** *(default)* — Make changes directly. You describe something and GenVibe builds it immediately. Best for quick apps and small edits.
* **Plan** — Discuss before building. GenVibe asks clarifying questions and/or writes an implementation plan, then waits for your go-ahead.

Switching to Plan doesn't change anything else — your prompt box, models, and Web/Mobile choice all work the same.

## How Plan mode works

1. Switch the dropdown to **Plan** and describe what you want.
2. If your idea needs a few decisions, GenVibe shows a short set of **multiple-choice questions** (for example: "Who signs in — just you, or a team?"). Pick an option, type your own, or skip.
3. GenVibe writes a clear **plan** — what it'll build, the key screens, any data it needs, and the build steps.
4. Review it. Then:
   * **Approve & build** — GenVibe starts building, following the plan.
   * Or reply with changes ("skip the calendar for now", "make it a single page") and it revises the plan.

Nothing is built and no code is scaffolded until you approve — so planning is a safe, no-commitment conversation.

## When to use it

* **Bigger apps** with several screens or features, where you want to agree on scope first.
* **Fuzzy ideas** where you're not sure exactly what you want yet — the questions help you decide.
* **Getting the data model right** before building on top of it.

For quick, obvious apps and small tweaks, plain **Build** mode is faster — just describe it and go.

## Tips

* Answer the questions honestly, or skip the ones you don't care about — GenVibe fills the rest with sensible defaults.
* You can keep refining the plan in chat before approving; treat it like briefing a teammate.
* Once you approve, you're in the normal build loop — keep chatting to refine, exactly like a Build-mode app.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.genvibe.pro/features/plan-mode.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.