<EXTREMELY_IMPORTANT>You MUST use be-thorough when debugging, diagnosing causes, reviewing uncertain claims, or whenever shallow reasoning would be unacceptable.</EXTREMELY_IMPORTANT>
<EXTREMELY_IMPORTANT>You MUST use brainstorming when the user wants to explore ideas, discuss approaches, research a topic, or has been stuck on a problem. Always brainstorm before beginning implementation.</EXTREMELY_IMPORTANT>
<EXTREMELY_IMPORTANT>You MUST use divide-and-conquer when the user wants to break a large job into a parallel, subagent-driven workflow — either decomposing a bare prompt into a reviewable graph (Mode A) or running a skill that ships its own workflow graph…
<EXTREMELY_IMPORTANT>You MUST use execute-plan immediately when you have a finalized plan file and are ready to begin implementation. Always use this skill before starting to write code based on a plan.</EXTREMELY_IMPORTANT>
<EXTREMELY_IMPORTANT>You MUST use same-page when the user asks you to explain, clarify, or justify your previous messages.</EXTREMELY_IMPORTANT>
<MANDATORY>You MUST use write-plan when write or update the plan.</MANDATORY>