/plan command creates a detailed project plan using the project-planner agent. This workflow generates only planning documents—no code is written.
Critical rules
Socratic Gate: The planner will ask clarifying questions before creating the plan.
Dynamic Naming: Plan files are named based on your task (e.g.,
PLAN-ecommerce-cart.md).When to use this
Large projects
Complex projects that need upfront planning
Time estimates
You need to understand effort and timeline
Team coordination
Multiple people need to understand the plan
Approval needed
Stakeholders need to review before implementation
How it works
Context check
The project-planner agent analyzes:
- Your project context
- Existing codebase (if any)
- Tech stack and patterns
Socratic questioning
Clarifying questions to understand:
- Exact requirements
- Constraints and preferences
- Success criteria
Output format
You’ll receive a plan file atdocs/PLAN-{task-slug}.md containing:
| Section | Content |
|---|---|
| Overview | High-level summary |
| Task Breakdown | Numbered steps and subtasks |
| Agent Assignments | Which agents handle what |
| Verification Checklist | How to verify completion |
| Time Estimates | Expected duration per phase |
Naming examples
| Request | Plan File |
|---|---|
/plan e-commerce site with cart | docs/PLAN-ecommerce-cart.md |
/plan mobile app for fitness | docs/PLAN-fitness-app.md |
/plan add dark mode feature | docs/PLAN-dark-mode.md |
/plan fix authentication bug | docs/PLAN-auth-fix.md |
/plan SaaS dashboard | docs/PLAN-saas-dashboard.md |
Usage examples
After planning
Once your plan is created, you can:- Review the plan: Read through and refine if needed
- Run
/create: Start implementation based on the plan - Modify manually: Edit the plan file directly if you want changes
Related workflows
- /brainstorm - Explore options before planning
- /create - Implement the plan
- /orchestrate - Use for complex multi-agent implementation