/plan Command
This command invokes the planner agent to create a comprehensive implementation plan before writing any code.What This Command Does
- Restate Requirements - Clarify what needs to be built
- Identify Risks - Surface potential issues and blockers
- Create Step Plan - Break down implementation into phases
- Wait for Confirmation - MUST receive user approval before proceeding
When to Use
Use/plan when:
- Starting a new feature
- Making significant architectural changes
- Working on complex refactoring
- Multiple files/components will be affected
- Requirements are unclear or ambiguous
How It Works
The planner agent will:- Analyze the request and restate requirements in clear terms
- Break down into phases with specific, actionable steps
- Identify dependencies between components
- Assess risks and potential blockers
- Estimate complexity (High/Medium/Low)
- Present the plan and WAIT for your explicit confirmation
Command Syntax
string
required
Natural language description of what needs to be implemented
Examples
Basic Usage
Example Output
Important Notes
If you want changes, respond with:- “modify: [your changes]”
- “different approach: [alternative]”
- “skip phase 2 and do phase 3 first”
Integration with Other Commands
After planning:- Use
/tddto implement with test-driven development - Use
/build-fixif build errors occur - Use
/code-reviewto review completed implementation
Related
- Agent:
~/.claude/agents/planner.md - Skills: Planning and architecture skills
- Commands:
/orchestrate,/tdd,/code-review