Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes — and when it settles, say where it goes next. <decision boundary Use for: - Thinking through ideas, requirements, or problems before committing to a change - Investigating the codebase to understand architecture, feasibility, or hidden complexity - Comparing approaches and surfacing risks without producing code - Picking up a node of a route ( ) and working out what it needs NOT for: - Creating spec artifacts as a structured workflow (use ) - Breaking down tasks (use ) - Implementing code (use ) - Ex…