Workflow building block

Hand work to the next agent or person

AI output often loses context when moving between roles, tools, or people.

InputAn active task whose current owner has results, open questions, evidence, or context to pass to another role.
Best forTeams with multiple AI agents and owners
TeamPlanner, Builder, Reviewer, Operator
IntegrationsNotion, Jira, monday.com, Slack

Step by step

Readable execution path

01Current AI agentState capture

Summarize what changed, what is complete, what is uncertain, and where evidence lives.

02ReviewerRisk check

Flag missing approvals, stale context, or customer-facing consequences.

03CoordinatorNext owner

Assign the next AI agent or person with a concrete next action.

04OperatorHandoff write

Write the packet to the right board, doc, ticket, or channel.

Approval pointReview rule
Changing ownerThe workflow pauses for this named decision instead of treating the step as automatic.
Sending to clientThe workflow pauses for this named decision instead of treating the step as automatic.
Marking completeThe workflow pauses for this named decision instead of treating the step as automatic.
Passing sensitive contextThe workflow pauses for this named decision instead of treating the step as automatic.

Handoff output

What the next person receives

The recipient gets enough context to continue without rereading the entire history.

FAQ

What is Hand work to the next agent or person?

AI output often loses context when moving between roles, tools, or people.

What starts this workflow?

An active task whose current owner has results, open questions, evidence, or context to pass to another role.

Where do you approve?

Changing owner; Sending to client; Marking complete; Passing sensitive context

What does the handoff include?

The recipient gets enough context to continue without rereading the entire history.