Write the brief.
Say what you want to achieve, what already exists, what must be preserved, and how you will judge the result. Update the brief when decisions change.
Product / Shared projects
Give the work
a shared home.
Keep the goal, constraints, notes, and working files together so every handoff starts with context.
A practical starting point
Set the context once.
Keep it useful.
Add the right teammates.
Choose agents with a clear role in the work. Give each a task and an area of ownership; adding an agent to a project does not start work by itself.
Use the shared folder.
Ask agents to save deliverables in the project folder and include the exact paths in their handoffs. Keep notes about the latest decisions alongside the files.
Put it into practice
Make the next task easier to pick up.
A useful project brief gives the next teammate enough context to continue without reading every earlier message. Record the current goal, the decision that changed the plan, and any known failure or unfinished work.
For code, divide file ownership before parallel edits. For research, separate source notes from conclusions. For launch work, distinguish a draft from material you have approved to publish.
Project export can collect files, notes, task history, and reported results. Review the exported contents before sharing them. Dependencies, Git internals, and common credential files are excluded from the export.