Create Plan

When to Use

• The user explicitly requests a plan for a coding task (feature, bug fix, refactor) before implementation begins.
• You need to organize work into ordered checklist items, including discovery, changes, tests, and rollout.
• The work benefits from a short, structured plan that can be reviewed and approved before coding.

When NOT to Use

• The request is already being implemented or no plan is needed (e.g., simple bugfix or documentation edit).
• You're in the middle of executing a plan and should focus on executing (use executing-plans).
• The task is exploratory, open-ended, or research-heavy without a concrete implementation path.

Goal

Turn a user prompt into a single, actionable plan delivered in the final assistant message.

Minimal workflow

Throughout the entire workflow, operate in read-only mode. Do not write or update files.