Start with the actual question
A message often contains several things at once: a fact, an assumption, a suggestion and a request. Before turning it into work, separate those parts. Ask what outcome is needed, what evidence is already available and who can make the decision. A clear question is more useful than an elaborate task created from a misunderstanding.
Keep the source beside the task
The next person should be able to see why the work exists. Keep the relevant conversation, document version or record attached to the proposed action. That does not mean copying every source into a broader room. The handoff must preserve the information boundary as well as the context.
Name the review point
Preparing a draft, updating an internal record and sending something outside the team are different actions. Say which one is intended. Record the responsible person and the point where they need to review the result. Approval should apply to a specific version, rather than a broad intention that might change later.
Close the loop with what happened
A queued request is not a completed action, and a lost response is not proof of failure. Record the actual result or the uncertainty that remains. The public workspace sample lets you explore that relationship with fictional records; it does not execute an agent or contact a customer.