Show what is ready.
Make the current work-item status visible so the receiving owner can distinguish a finished input from an unfinished review.
Pass the work. Keep the context.
A handoff is not just a change of owner. The next person needs the current state, the decisions behind it, and the question that still needs an answer. Keep those together.
The next contributor should not have to reconstruct the story.
Scoped keeps issues, comments, and attributed activity in the project record. People and authorized agents can return to the same work context even when the conversation or tool changes.
Carry open questions forward.
Record the remaining decisions alongside the handoff rather than burying them in a separate conversation.
Keep changes attributable.
People and MCP connections contribute to the same activity record, with the authorizing person and connection source visible.
A handoff with a readable history.
Give the next contributor access to the relevant project, recent discussion, and owned work items. An external agent can help summarize that context and post an authorized handoff comment.
A closer look at ScopedScopedProject context
Current work state and ownership in one record
Comments that preserve decisions and next steps
Attribution for authorized agent contributions
Move a campaign from design to production.
The designer records the agreed layout. A content decision remains open, so the producer receives both the completed design context and a clear next step with an owner.
Update the design issue with the current decision and status.
Record the remaining content question and responsible owner.
Give the production owner the handoff issue and its recent context.
A few useful answers.
Does a handoff automatically execute the next task?
No. Scoped coordinates work state. A person or external agent carries out the next task in the appropriate environment, within the authority it has been given.
Can different agents contribute to the same handoff?
Compatible MCP clients can access the workspace and permissions you authorize. Their updates return to the shared work record with person and connection attribution, rather than becoming a private conversation only one agent can see.
Does this depend on an Aether connection?
No. The project record is held in Scoped. Aether provides a separate memory and retrieval capability; this example does not assume a live automatic integration.