Run a Two-Bot Launch Relay

Level: Advanced · No Code · 60 Minutes

Create two specialist Bots and have one Bot hand finished work to the other. A Source Editor builds a brief from a public page. It then invokes a Launch Producer, which reads the brief from the shared cloud computer and returns a ready-to-review announcement and run of show. Nothing is published or sent.

What you’ll do and learn:

Give each Bot one job: Source Editor owns the facts and Launch Producer owns the final materials.
Let one Bot call the other: Source Editor invokes Launch Producer after you approve the brief, so you do not relay the work by copying and pasting.
Use shared files: Both Bots work from the same launch-desk folder on the cloud computer.

Steps:

Choose a public page for an event, project, club, or product you can describe accurately, and copy its URL. Write down three constraints for the announcement: audience, tone, and call to action. You will replace [AUDIENCE], [TONE], and [CALL TO ACTION] in the prompt below.
Create a Bot named Source Editor. In Settings, paste this into the Job or Instructions field:
> “Verify facts, preserve source links, use Unknown for missing information, and save work as launch-desk/source-brief.md. Ask before contacting anyone or publishing.”
Create a Bot named Launch Producer. In Settings, paste this into the Job or Instructions field:
> “Read an approved brief and create a 120- to 180-word launch-desk/announcement-draft.md plus launch-desk/run-of-show.csv with at least five rows. The run of show must use the columns Time, Owner, Action, and Status. Use only the approved brief. Ask before sending, publishing, purchasing, or changing an external system.”
In the existing chat with Source Editor, send this request:
> “Build the brief from [SOURCE PAGE URL]. Use these announcement constraints: Audience: [AUDIENCE]; Tone: [TONE]; Call to action: [CALL TO ACTION]. Verify facts, preserve source links, use Unknown for missing information, save the brief as launch-desk/source-brief.md, and stop for my approval before handing it to Launch Producer. Do not contact anyone or publish anything.”
Open source-brief.md on the shared computer. If the Markdown is hard to review there, ask Source Editor to also save launch-desk/source-brief.txt and review that copy. Use the same plain-text fallback for any later .md file. Correct unsupported facts, then tell Source Editor to invoke Launch Producer and bring the result back to the same conversation. Do not open a separate chat to repeat the assignment.
Wait for Launch Producer to return the 120- to 180-word announcement and a run of show with at least five rows. Confirm that both files are in the launch-desk folder and use only the approved brief.
Ask Source Editor to compare both files with the approved brief and save launch-desk/qa-notes.md with either Pass or a short list of fixes. If it finds a problem, Source Editor must route only those fixes back to Launch Producer.

Capture the visible handoff and the final launch-desk folder. Do not send or publish the announcement.

You are finished when one conversation shows the Bot-to-Bot handoff, the three deliverable files exist, and qa-notes.md says Pass.

Examples:

Club event. Source Editor verifies the event facts; Launch Producer creates the attendee announcement and run of show.
Community workshop. Source Editor verifies the instructor, venue, and materials; Launch Producer creates the participant announcement and setup schedule.
Volunteer drive. Source Editor verifies shifts and eligibility; Launch Producer creates the recruitment announcement and organizer schedule.
Product launch. Source Editor verifies features, availability, and price; Launch Producer creates the announcement and release-day run of show.

What to submit:

A screenshot showing Source Editor invoking Launch Producer and bringing the result back.
The final announcement and run of show, or screenshots that show the complete files.
A screenshot of the launch-desk folder and qa-notes.md showing Pass.