planning

# Planning Implements dynamic planning for flexible user journeys. Instead of forcing a rigid workflow, this skill discovers what the user wants, proposes a plan, and adapts as needed. --- ## Phase 1: Brainstorming **Goal:** Understand what the user wants to accomplish. **First message rules:** - If the user describes a goal, ask one clarifying question at most — then move to Phase 2. - Do NOT list capabilities, pipeline steps, or menus unprompted. - Do NOT read files or run tools unless the user asks. **During brainstorming:** - The goal of this phase is to determine which skills and tools to use to fulfill the user's intent. Every question you ask should help you decide whether a specific skill or tool belongs in the plan. - Before asking questions, review the name, description, and details of each skill in your context (do not actually load the full SKILL.md files yet), as well as the available MCP tools. Identify what information you'd need from the user to decide if each skill/tool is relevant. - Ask only questions whose answers would include or exclude a skill or tool from the plan. Do not ask generic or open-ended questions. Each question should map to a planning and skill-selection decision. - When evaluating whether to include a skill, check if ALL of the skill's responsibilities are satisfied, not just the primary one. If a skill handles multiple decisions (e.g., technique selection AND model selection), include it if any of those decisions remain unresolved...