# Plan Mode





<DocVideo src="features/modes/switch-to-plan" alt="Clicking the Build button in the chat input to switch to Plan, then typing a question" width="960" height="252" />

Plan Mode is your development and debugging partner inside Ideavo. It helps you think through problems, design solutions, and diagnose issues — directly in conversation.

<Callout type="info">
  **Ideavo has two modes:**

  * **Plan Mode** — think through the problem, explore options, and decide on an approach
  * [**Build Mode**](/docs/features/build-mode) — implement changes and verify the outcome

  Plan Mode is for decision-making. Build Mode is for execution. You can switch between them at any time.

  Both modes are available in [**Tasks**](/docs/features/tasks) as well.
</Callout>

<Cards>
  <Card title="Conversational & read-only" icon="<BiConversation />" description="Unlike Build Mode, Plan Mode does not modify code." />

  <Card title="Agentic reasoning" icon="<RiRobot3Fill />" description="Reasons across multiple steps — searches files, inspects logs, queries databases — purely for analysis." />

  <Card title="Actionable plans" icon="<NotebookPen />" description="Produces a clear step-by-step plan to implement a feature or fix a bug." />

  <Card title="Seamless handoff" icon="<ArrowRightLeft />" description="Switch to Build Mode when ready — your plan carries directly into implementation." />
</Cards>

## Two ways to enter Plan Mode [#two-ways-to-enter-plan-mode]

* **Start in Plan Mode** — Begin a new project or feature by thinking it through before any code is written.
* **Switch to Plan Mode mid-session** — Pause at any point during development to step back, investigate an issue, or rethink an approach.

Both paths are valid. Plan Mode is designed to fit wherever you need to think first.

### Implementing a Plan [#implementing-a-plan]

<Steps>
  <Step>
    Generate a plan in Plan Mode by describing your goal or problem.
  </Step>

  <Step>
    Switch to Build Mode.
  </Step>

  <Step>
    Ask Ideavo to implement the plan. Build Mode will make the necessary code
    changes.
  </Step>
</Steps>

## Best Use Cases for Plan Mode [#best-use-cases-for-plan-mode]

* **Deep-dive debugging** — Investigate issues thoroughly before requesting a fix
* **Data modeling** — Plan database schemas and relationships for solid system architecture
* **Feature design** — Identify the minimal, necessary changes for new functionality
* **Quality improvements** — Request concrete tips to enhance performance, security, or UX
* **Impact analysis** — Understand how proposed features affect structure and dependencies

### Example Prompts [#example-prompts]

Not sure how to start? Here are prompts that work well in Plan Mode:

**Debugging**

```
Users report the login form doesn't work on mobile. Help me figure out why before we change anything.
```

**Feature design**

```
I want to add a notification system. Walk me through what components, database tables, and API endpoints I'd need.
```

**Architecture**

```
What's the best way to handle file uploads in this project? Give me the options and their tradeoffs.
```

**Security review**

```
Review my current authentication setup and tell me what security improvements I should make.
```

## What a Plan Includes [#what-a-plan-includes]

When Plan Mode produces a formal plan, it typically covers:

* A high-level overview of the proposed approach
* Key decisions, assumptions, and constraints
* Components, data models, and API changes involved
* Step-by-step implementation sequencing
* Diagrams where relevant — schemas, flows, or architecture

Not every Plan Mode conversation produces a formal plan. Many end with clarity, a direction, or an answer — and that's a valid outcome too.

### FAQ [#faq]

<Accordions>
  <Accordion title="Does Plan Mode ever change my code?">
    No. Plan Mode is strictly read-only. Code changes only happen after you
    switch to Build Mode and ask Ideavo to implement.
  </Accordion>

  <Accordion title="Can I use Plan Mode just to ask questions?">
    Yes. Not every conversation needs to produce a plan. You can use Plan Mode
    to explore ideas, understand your codebase, or get answers — without
    committing to any implementation.
  </Accordion>

  <Accordion title="Can I use Plan Mode for debugging?">
    Yes. Plan Mode is well suited for investigating issues safely — inspecting
    logs, tracing errors, and understanding root causes — before any fix is
    applied.
  </Accordion>

  <Accordion title="When should I switch from Plan Mode to Build Mode?">
    Switch when you have a clear direction and are ready to make changes. If
    you're still exploring or uncertain, stay in Plan Mode.
  </Accordion>
</Accordions>
