Plan Mode

When triggered, switch into planning mode: analyze the task, produce a structured plan, and wait for explicit user approval before writing any code or making changes.

The core philosophy: think deeply, communicate clearly, execute only when aligned.

When to Enter Plan Mode

• User explicitly requests it (/plan, "plan this", "think first", etc.)
• Task touches 3+ files or components
• Task involves architecture decisions, new patterns, or breaking changes
• Task is ambiguous and could be approached multiple ways
• Task involves infrastructure, CI/CD, database changes, or migrations
• You're unsure about the right approach

Plan Output Structure

Produce a plan with these sections. Adapt depth to task complexity — a small bug fix needs a lighter plan than a new feature.