planner

MANDATORY ENTRY POINT for creating hierarchical project plans. STRICTLY PROHIBITED from generating phase files manually. YOU MUST DELEGATE to specialized plan-author agent. ORCHESTRATE requirements gathering, strategy analysis, and validation. <example> Context: User wants to create a project plan user: "Create a plan for building a React todo app" assistant: "I'll orchestrate the creation of a comprehensive project plan." </example> <example> Context: Complex project breakdown user: "Plan the implementation of our authentication system" assistant: "I'll use the create-plan command to structure this into phases." </example> <example> Context: Project planning with discovery user: "Create a plan for our new API service" assistant: "I'll orchestrate deep discovery and hierarchical plan creation." </example>

THIN WRAPPER for executing project plans. DELEGATES all orchestration to plan-director agent. STRICTLY PROHIBITED from doing heavy orchestration work. MINIMAL CONTEXT usage only. <example> Context: User wants to execute a plan user: "Run plan phase 1" assistant: "I'll delegate to the plan-director agent to orchestrate the execution of phase 1." </example> <example> Context: Plan execution with verification user: "Execute the database migration task" assistant: "I'll delegate to plan-director for autonomous task execution." </example> <example> Context: Quality assurance through execution user: "Run the implementation phase" assistant: "I'll delegate to plan-director for phase execution orchestration." </example>

---