Plan Mode: How to Get a Plan Before GenMB Builds

What Is Plan Mode?

GenMB used to have a Plan Mode toggle. It is gone, and you do not need it. The chat now works out what you want from what you type:

• Ask a question, or ask for a plan, an explanation or an audit, and the AI answers without changing your app. That reply is free.
• Ask for a change, and GenMB builds it, then checks it.

So "Plan Mode" is now just a way of asking. Instead of letting the AI jump straight into code, you ask it to lay out what it would build, how the parts connect and what decisions it would make. You read the plan, adjust it, and then tell it to go ahead.

Think of it as the difference between a builder who starts laying bricks immediately versus one who walks you through the blueprints first. Both get the job done, but reviewing the blueprints catches misunderstandings early, especially on big features.

How Plan Mode Works

Getting a plan takes four steps, all in the chat panel of your app.

Step 1: Ask for a Plan

Say what you want and make it clear you want a plan first. For example: "Plan how you would add a team page with roles and invites. Don't change anything yet."

Step 2: Read the Plan

The AI replies with a plan and leaves your app as it is. A good plan usually covers:

• Feature breakdown: each feature and the parts it needs
• What changes: which screens and parts of your app would be added or changed
• Data flow: how information moves between screens
• Decisions: the approach it would take and why
• Build order: what it would do first

Step 3: Adjust It

Reply in chat to shape the plan. You can:

• Ask for changes ("Move the sign-in step before the dashboard loads")
• Add missing requirements ("Also include a settings page")
• Remove features ("Skip the analytics section for now")
• Ask questions ("Why did you pick a table instead of cards?")

None of this changes your app.

Step 4: Ask It to Build

When you are happy, say "go ahead and build this". GenMB makes the change using the plan from the conversation, then checks it, so the result has better structure and fewer integration issues.

When to Use Plan Mode

Asking for a plan first takes one extra message. Here is when that pays off:

Complex Multi-Feature Changes

If your request covers more than three distinct features, a plan helps you see whether the AI has understood how they fit together before anything is built.

Changes with Data Dependencies

When features depend on each other (a dashboard that reads the same data a form writes to, or a cart that needs to stay in sync with stock), a plan maps out those links before anything changes.

When Structure Matters to You

If you care about how your app is organized, a plan lets you review and influence the approach before any code is written.

When You Are Unsure About Scope

If your idea is broad and you want to see how the AI reads it, ask for a plan. You can refine the direction without waiting for a full build.

Plan Mode vs Direct Generation

Here is a practical comparison:

Just Ask for the Change

• GenMB builds and checks the change straight away
• Fastest for small changes and clear requests
• Big first requests are still planned and built step by step on their own (Agent Mode), with nothing to switch on

Ask for a Plan First

• The AI shows its plan and changes nothing
• You can review, adjust and approve the approach
• Better for big, multi-feature changes where you want a say in the approach
• One extra message, and the planning reply is free

A good rule of thumb: if your request is under 3 sentences and describes a single change, just ask for it. If it is a paragraph or more with several features, ask for a plan first.

Reviewing and Editing Plans

The plan appears as a normal reply in the chat panel. Here is an example of what one looks like:

`

Plan for: Project Management Dashboard

1. Layout & Navigation

• Sidebar with navigation links (Dashboard, Projects, Tasks, Team)
• Top bar with search and user profile
• Responsive: sidebar collapses to a menu button on mobile

1. Dashboard View

• KPI cards: total projects, active tasks, team members, completion rate
• Recent activity feed
• Upcoming deadlines chart

1. Projects List

• Table with columns: name, status, progress, due date
• Create project form
• Filter by status (active, completed, on hold)

1. Task Board

• Columns: To Do, In Progress, Review, Done
• Drag and drop between columns
• Task cards with assignee, priority and due date

1. Saved Data

• Projects and tasks saved so they are there next time

`

You can respond with edits like:

"Add a team members page to section 4 and use a chart for the KPI cards instead of simple numbers"

The AI updates the plan and shows it again. When it looks right, reply "build it".

Examples of Plan Mode Output

Simple Change (No Plan Needed)

Request: "Add a tip calculator to the footer"

A plan here would be one or two lines. Just ask for the change.

Big Change (Plan Recommended)

Request: "Plan an employee directory with department filtering, an org chart view, profile pages, and a search that works across name, title, and department"

The plan maps out the data, four distinct views, shared search and how they connect, catching questions like where the org chart data comes from and how filtering works with the tree view.

Best Practices

Be Detailed in Your Request

The more detail you give, the better the plan. Include the features, how the data relates and how you want it to look, so the AI has enough to work with.

Read the Plan Before You Say Build

The plan shows how the AI understood you. If it misread something, catching it now saves a round of fixes later.

Ask for an Explanation Any Time

You can also ask how something in your app works ("Explain how the booking page saves a reservation") or for an audit ("Check my app for anything broken on mobile"). These replies never change your app.

Summary

There is no Plan Mode toggle any more: just ask in chat. Ask for a plan and GenMB answers without changing your app. Adjust the plan as much as you like, then ask it to build. For big, multi-feature changes this gives you a say in the approach, catches misunderstandings early and leads to better results.