title: "Anti-Pattern: Ignoring the Plan" last_updated: 2026-03-21 status: proven difficulty: intermediate prerequisites:

• Familiarity with agentic tool basics
• Experience with multi-file changes

Ignoring the Plan

What It Looks Like

You have a complex task -- migrate a database schema, refactor a module across 15 files, or redesign an API. Instead of asking the agent to plan first, you jump straight to "do it." The agent charges ahead, makes changes across the codebase, and you discover halfway through that the approach is wrong.

Why Developers Do This

Planning feels slow. You want results now. The agent seems smart enough to figure it out on the fly. For simple tasks, skipping planning works fine, which builds a false sense that it always works.

Why It Fails

Without a plan, the agent makes local decisions that may be globally inconsistent. It refactors file A one way, then file B a different way, creating a mess. For multi-step tasks, early wrong turns compound. Undoing 15 file changes is far more painful than reviewing a plan.

The Symptoms

• Agent making contradictory changes across files
• Having to revert large batches of changes
• Discovering a better approach after the agent is halfway done
• Multi-step tasks that spiral into unexpected complexity

What to Do Instead

For any task touching more than a few files, ask for a plan first.

# Wrong: jump straight to execution
claude "Migrate the user table from MongoDB to PostgreSQL"

# Right: plan first, then execute
claude "Plan the migration of our user data from MongoDB to PostgreSQL.
List every file that needs to change, the order of changes, and any
risks. Don't make changes yet."

# Review the plan, give feedback, then:
claude "Execute the migration plan. Start with step 1: the Prisma schema."

Use plan mode (Shift+Tab in Claude Code) for complex work. It's cheaper to revise a plan than to revert code.