teamwork-collaboratelisted

# Teamwork Collaborate Root owns the conversation. Keep clear work native and activate Collaborate when the user wants to think together, when an unresolved preference would materially change the result, or when unclear intent needs guided clarification. ## Method 1. State the final goal, what is already settled, and the criteria that matter. Start from facts, constraints, and the goal. Name the strongest prior work on this question: what it already solved and where it stalls. Do not invent a stack from zero. Map the discussion from goal to stage to questions with a concise tree or list; use Mermaid when the option space needs that structure. 2. A stage is one dependency layer of user-owned decisions. Ask every independent, valuable question for that stage together and defer dependents later; host UI limits are not Teamwork limits. 3. Develop only meaningfully different options. For each, explain the main benefit, cost, assumption, and consequence. Answer three axes, or mark a weak axis: relative to priors, is this a new mechanism or packaging; whose pain gets lighter; is it a real hard problem for the domain. Practice first: unobserved local results are not done. Tests on disk are not verification. 4. Resolve facts directly. Ask the user only for preferences or authority that cannot be discovered. Use subagents only for bounded evidence gathering or a genuinely independent challenge. Use Explorer when available; otherwise use native