planner
Breaks down complex tasks into interactive, sequential plans with revision and branching for project planning, system design, and architectural decisions.
Instructions
Breaks down complex tasks through interactive, sequential planning with revision and branching capabilities. Use for complex project planning, system design, migration strategies, and architectural decisions. Builds plans incrementally with deep reflection for complex scenarios.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| step | Yes | Planning content for this step. Step 1: describe the task, problem and scope. Later steps: capture updates, revisions, branches, or open questions that shape the plan. | |
| model | Yes | Currently in auto model selection mode. CRITICAL: When the user names a model, you MUST use that exact name unless the server rejects it. If no model is provided, you may use the `listmodels` tool to review options and select an appropriate match. Top models: gemini-2.5-pro (score 100, 1.0M ctx, thinking, code-gen); gemini-3-pro-preview (score 100, 1.0M ctx, thinking, code-gen); gemini-2.5-flash (score 61, 1.0M ctx, thinking); gemini-2.0-flash (score 56, 1.0M ctx, thinking); gemini-2.0-flash-lite (score 42, 1.0M ctx). | |
| branch_id | No | Name for this branch (e.g. 'approach-A', 'migration-path'). | |
| step_number | Yes | Current step number in work sequence (starts at 1) | |
| total_steps | Yes | Estimated total steps needed to complete work | |
| continuation_id | No | Unique thread continuation ID for multi-turn conversations. Works across different tools. ALWAYS reuse the last continuation_id you were given—this preserves full conversation context, files, and findings so the agent can resume seamlessly. | |
| is_branch_point | No | True when this step creates a new branch to explore an alternative path. | |
| branch_from_step | No | If branching, the step number that this branch starts from. | |
| is_step_revision | No | Set true when you are replacing a previously recorded step. | |
| more_steps_needed | No | True when you now expect to add additional steps beyond the prior estimate. | |
| next_step_required | Yes | Whether another work step is needed. When false, aim to reduce total_steps to match step_number to avoid mismatch. | |
| revises_step_number | No | Step number being replaced when revising. | |
| use_assistant_model | No | Use assistant model for expert analysis after workflow steps. False skips expert analysis, relies solely on your personal investigation. Defaults to True for comprehensive validation. |