Delegate work and hand off conversations
Follow parent and child work without losing decisions or ownership.
Delegation creates or assigns a bounded piece of work to another role or session. A handoff changes who continues a conversation when that control is available. Neither automatically supplies context that was never recorded.
Define the handoff
State the outcome, repositories, constraints, and completion evidence. Identify decisions the receiving role must preserve. A useful handoff includes a link to the source task or specification and a short explanation of what remains.
For example, Product can establish the agreed behavior and pass implementation context to Engineering. Chief can coordinate related tasks and follow delegated results. The supported controls depend on the role and conversation.
Follow child work
Open child session and conversation links from the parent or task references. The child can have its own execution state, questions, and outputs. An idle parent does not establish that all delegated work is finished.
Answer questions in the work that asked them. A parent summary helps coordination, but review the child output for implementation evidence and reported checks.
Preserve delivery responsibility
Distinguish a task's human owner, agent assignment, and linked delivery sessions. A reference link alone does not make a session a required delivery contribution. Read task progress when completion depends on several sessions.
Avoid starting duplicate implementation because you do not immediately see a child in the top-level session list. Inspect the existing links and status first.
For active guidance, use steering. For a different independent objective, start a new session.