Before you start
- A saved artifact and a teammate who needs to review or continue it.
- A clear distinction between viewing, commenting and editing.
Connect your AI to the work
Open Stash and choose Connect your AI tools. Authorize your client, then check that it can read the intended work before asking it to edit. The connection uses MCP, a way for AI tools to read and update work in another service.
For a new publication, explicitly ask for private access. New MCP artifacts otherwise allow public editing. Your selected space is the default publishing destination, not a limit on everything the connection can access.
See the connection and handoff workflow. Client availability and workspace permissions can vary.
The workflow
- 01
Choose the handoff baseline
Select a known version rather than saying “use the latest” in a long chat. Record the link and version identifier, what works and what is incomplete. If there are multiple experiments, identify the preferred direction and explain which alternatives should not be continued.
- 02
Write a compact project brief
Use five headings: goal, current state, decisions, open issues and next task. Include relevant source and asset links with permission to access them. Preserve the reasons behind unusual choices. A list of every prompt is less useful than the small set of decisions that still constrain the work.
- 03
Grant suitable access
A fixed-version comment invitation suits a reviewer. Continuing the project requires appropriate edit access to the work or space. Ask the recipient to use their own AI connection and identity. Never send your private profile recovery link as a collaboration link; it restores your profile rather than granting a bounded review permission.
- 04
Ask for a readback
Before any edits, ask the teammate or their AI to identify the current version and summarize the next task. Resolve missing assets or access problems now. If they cannot read the source, stop and fix the handoff instead of encouraging a visually similar reconstruction.
- 05
Make one small continuation
Begin with one bounded change and inspect the new version together. Check that the original still exists and that access remains correct. Update the brief with the new version and remaining work. Treat the handoff as complete when the recipient can continue, not when a link has been sent.
WORKED EXAMPLE
Pass the workshop prototype to a developer
The designer has selected the cream direction but the booking flow is still simulated.
Starting point
“Here is the project, finish it” omits the chosen branch and makes the demo appear further along than it is.
A clearer result
“Continue version [ID]. Keep the selected layout. Next: propose the real booking integration. The current button is only a simulation; do not connect payments yet.”
Check the result
- The teammate can read the intended source.
- The brief names the unfinished behavior.
- No personal recovery link or secret is included.
A prompt you can use
Replace the bracketed fields with your project details. Check what the AI can access before requesting changes.
Read [work link] and this handoff brief: [brief]. Before editing, confirm the version, chosen direction, fixed decisions, known limitations and next task. List missing access or assets. Do not infer missing requirements. After I confirm the task, append a new version while preserving the baseline and current access.Download the brief, prompt and checklist ↓
Questions & answers
How do I hand an unfinished AI project to a teammate?
Share a known version with a handoff brief and the access needed to continue. Ask the recipient to confirm the baseline, then make one small verified change. Do not transfer your personal recovery link.
Should I share the whole conversation?
Usually a reviewed summary plus the source is more useful. Include important decisions and unresolved questions. Share conversation material only when it is necessary and appropriate for the recipient.
Can a comment-only reviewer continue editing with AI?
Comment permission does not grant source-editing permission. Continuing the work needs suitable artifact or space access and an authorized AI connection.
What if the recipient cannot open the work?
Check the invitation scope, expiry and recipient access. Confirm that their AI connection uses a profile with permission. Avoid making a private project public merely to work around an access mistake.
Keep in mind
- A handoff brief does not migrate model memory or automatically grant access to externally linked files.
Put it into practice.
Start with the example or bring a small project of your own.
Open the project in Stash ↗