Plan Mode

Plan mode is a workflow where Claude researches your codebase and creates a detailed implementation plan before writing any code. Instead of jumping straight into edits, Claude first explores the relevant files, identifies dependencies, and outlines the steps it will take. You review and approve the plan before any changes are made.

What is Plan Mode?

In a normal session, Claude reads your prompt and starts implementing right away. Plan mode adds a deliberate planning phase between the prompt and the implementation. This is especially useful for complex tasks where understanding the full scope of changes matters.

How to Enter Plan Mode

You can activate plan mode by including the word "plan" in your prompt or by being explicit about wanting a plan first:

Plan how to add authentication to this app using Clerk.
Do not implement anything yet.

I need to refactor the data fetching layer. Create a plan
first, then wait for my approval before making changes.

The key is to tell Claude you want a plan, not immediate action.

What Happens During Planning

When Claude enters plan mode, it goes through several steps:

1. Research

Claude reads relevant files in your project to understand the current state. It uses Glob to find files, Read to examine them, and Grep to search for patterns.

2. Exploration

Claude traces dependencies, identifies affected components, and maps out how different parts of the codebase connect to the task.

3. Plan Writing

Claude produces a structured plan that typically includes:

  • A summary of the current state
  • A list of files that will be created, modified, or deleted
  • Step-by-step implementation details
  • Potential risks or considerations

Reviewing and Approving Plans

After Claude presents the plan, you can:

  • Approve it — Tell Claude to proceed with implementation.
  • Modify it — Ask Claude to adjust specific steps or change the approach.
  • Reject it — Ask for a completely different strategy.
This plan looks good, but skip step 3 since we already
have error handling in place. Go ahead and implement.

When to Use Plan Mode

Plan mode is most valuable for:

  • Large features that touch multiple files or systems
  • Refactoring where understanding the existing code is critical
  • Unfamiliar codebases where you want Claude to explore before acting
  • Architecture decisions where the approach matters as much as the code

For small, straightforward tasks like fixing a typo or adding a simple component, plan mode adds unnecessary overhead. Use direct execution instead.

Example Plan Workflow

Here is a typical plan mode interaction:

You: Plan how to add dark mode support to the app.

Claude: I will investigate the current styling setup...
[reads tailwind.config.ts, layout.tsx, globals.css]

Here is my plan:
1. Update tailwind.config.ts to enable dark mode with "class" strategy
2. Create a ThemeProvider component using next-themes
3. Add a ThemeToggle button component to the header
4. Update CSS variables in globals.css for dark mode colors
5. Test by toggling the theme in the browser

Shall I proceed?

You: Looks good. Go ahead.

Claude: [begins implementation]

This workflow gives you full visibility into what Claude intends to do before any files are touched, reducing surprises and making it easier to catch issues early.