Hand work between teammates with an explicit packet

A reliable handoff names the files, accepted decisions and remaining questions. Use an explicit second task rather than assuming teammates share every detail of a prior conversation.

Start with a small handoff

Select a role by its working guide and deliverables, then verify the connected AI tool and workspace. Keep the first run small enough that you can inspect every output. The desktop needs to stay running while work executes. Marketplace sign-in, model access and file-generation tools are separate setup requirements; a success in one does not prove the others are ready.

Inputs for this workflow: Reviewed output from the first task and the next role’s objective.

Work through the task

1. Freeze the accepted input version.
2. Give the next teammate a bounded transformation.

A brief you can adapt

Use reviewed-findings.md to draft a six-slide outline. Preserve source references, add no new research and list questions that block a final slide.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Compare the second output with the accepted first-stage packet and check for unsupported additions.

Where this approach can fail

This is a manual workflow pattern, not a claim that OfficeCubs provides an automatic multi-agent orchestration pipeline.

For the related desktop setup, see first task.