create_plan
Generate structured implementation plans for software development tasks by analyzing codebase context, identifying dependencies and risks, and creating actionable step-by-step guides.
Instructions
Generate a detailed implementation plan for a software development task.
This tool enters Planning Mode, where it:
Analyzes the codebase context relevant to your task
Generates a structured, actionable implementation plan
Identifies dependencies, risks, and parallelization opportunities
Creates architecture diagrams when helpful
When to use this tool:
Before starting a complex feature or refactoring task
When you need to understand the scope and approach
To identify potential risks and dependencies upfront
When coordinating work that touches multiple files
What you get:
Clear goal with scope boundaries
MVP vs nice-to-have feature breakdown
Step-by-step implementation guide
Dependency graph showing what can run in parallel
Risk assessment with mitigations
Testing strategy recommendations
Confidence score and clarifying questions
The plan output includes both a human-readable summary and full JSON for programmatic use. By default, plans are persisted so they can be executed later via plan_id.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task | Yes | The task or goal to plan for. Be specific about what you want to accomplish. | |
| max_context_files | No | Maximum number of files to include in context analysis (default: 10) | |
| context_token_budget | No | Token budget for context retrieval (default: 12000) | |
| generate_diagrams | No | Generate architecture diagrams in the plan (default: true) | |
| mvp_only | No | Focus on MVP features only, excluding nice-to-have (default: false) | |
| auto_save | No | Persist the generated plan for later use (default: true) | |
| save_name | No | Optional custom name for the saved plan | |
| save_tags | No | Optional tags for the saved plan | |
| save_overwrite | No | Overwrite existing plan with same ID when auto-saving (default: false) |