• Only use the course sample data or data you invent in class.
• Never enter classified or official information, real unit names, locations, call signs, personnel details, real equipment designations, real plans, orders or reports, or anything copied from a work system.
• No personal or work accounts. Do not connect email, calendars, drives or other connectors to your own accounts.
• No photos or screenshots of work systems, documents, maps or screens.
• Label everything: every output carries the words FICTIONAL TRAINING DATA.
• Human approval stays with you. Read what the agent is about to do before you approve it, and check every output.
• If in doubt, leave it out and ask an instructor.

Laptop 1 Team Manager: Joanne Ng, Events Manager
Laptop 2 Client Helper: Marcus Lee, Client Relations
Laptop 3 Marketing Helper: Priya Nair, Marketing
Laptop 4 Shopping Helper: Daniel Koh, Purchasing (stops before payment)
Laptop 5 Event Planner + Money Helper: Mei Ling Tan, Operations and Finance

08:30
Doors open - sit with your group
09:00-09:05
Welcome
09:05-09:45
Introductions, day starter, role cards
09:45-10:25
Module 1 - Hire your Team Manager (+ debrief)
10:25-10:40
Break
10:40-11:30
Module 2 - CRAFT prompts & the 5 heads
11:30-12:30
Module 3 Part 1 - Specialists & real work
12:30-13:15
Lunch - builders and testers swap
13:15-14:30
Module 3 Part 2 - Video, shopping, skill & routine
14:30-14:45
Break
14:45-15:45
Module 4 - Swap & try to trick it
15:45-16:15
Module 5 - Next hires & next-step plan
16:15-16:45
Demos
16:45-17:00
Wrap-up & reset

1. Don't delete or rename other people's bots. If something looks wrong, tell its builder or the trainer.
2. Name bots exactly as shown on the org chart (e.g. 'Poster Maker', not 'poster bot').
3. Only the group driver types into the bot. Everyone else reads prompts out, watches and checks.
4. No real personal or client data.
5. Stop before Send or checkout. A human gives the OK first. Nothing is paid for, ever.
6. Tell the trainer before creating a routine.
7. Pop-up, captcha or login page? Stop and raise your hand. Don't click Connect, Allow or Sign in, and never type a password for a real account.

The trainer writes your tasks on the whiteboard. In Module 1, Team Manager Tester photographs it and Team Manager turns it into a task list.

See Day Guide page 3.

Driver: Team Manager Builder, on the shared Grokbot login.

Jobs:
• Team Manager Builder - Driver: click New Bot (+), or press Cmd+N (Mac) / Ctrl+N (Windows). Name it exactly Team Manager. Send setup prompt ‘Set up the Team Manager’ (Day Guide p.7) (the case date, 3 Dec 2026, is already in it). Send Team Manager Tester's photo with ‘Turn the whiteboard photo into a task list’ (Day Guide p.7) (drag the photo into the chat, or use the attach button). Then type Client Helper Builder's and Marketing Helper Builder's questions and Client Helper Tester's safety test, one at a time.
• Team Manager Tester - Scribe, then Recorder: photograph the whiteboard (straight on, all writing visible). Unclear? Use the Backup Whiteboard or launch-notes.docx. Write a clean task list in your group's Module 1 (09:45) Padlet post. Check the bot's list line by line; read out ‘Check the task list for misses’ (Day Guide p.7), then ‘Add a missed task’ (Day Guide p.7) for any miss. Then post the findings: what it got right or wrong, and where it stopped to ask.
• Client Helper Builder and Marketing Helper Builder - Prompt writers: each write 2 questions for Team Manager. Copy ‘Ask the Team Manager a question’ (Day Guide p.8) and change only the [task] part. Hand them to Team Manager Builder one at a time.
• Client Helper Tester - Safety tester ('try to make it say no'): use ‘Safety test’ (Day Guide p.8): a request Team Manager should refuse or check with you first. Hand it to Team Manager Builder and record the answer.
• Marketing Helper Tester - Org-chart tester: for each task it routes, mark on the org chart whether it went to the right head.

CRAFT in one line: Context (background) · Role (who the bot is) · Action (the job, one verb) · Format (what the answer looks like) · Tone (style) · ! Never ... without asking me. In Module 1 (09:45), just copy ‘Ask the Team Manager a question’ and change only the [task] part.

Pop-up, captcha or login page? Stop, don't click, raise your hand. The trainer handles it. Never type a password for a real account.

Optional: swap the typing seat every 5 minutes.

After debrief: click the bot's name to see its details.

Prompts: Day Guide pages 6-7 / your role card. New words: Day Guide page 5.

Post back: the task list (screenshot), your questions + answers, the safety test result and the org-chart check.

• Task list: Team Manager Tester's clean task list (scribe) and a screenshot of Team Manager's prioritised list (task, head, urgency) and any misses found.

• Questions: your ‘Ask the Team Manager a question’ (Day Guide p.8) questions and the answers: which head, and why.

• Safety test: your ‘Safety test’ (Day Guide p.8) request and what Team Manager said.

• Findings (recorder): what it got right or wrong, and where it stopped to ask.

• Task list: Event Planner Tester's clean task list (scribe) and a screenshot of Team Manager's prioritised list (task, head, urgency) and any misses found.

• Questions: your ‘Ask the Team Manager a question’ (Day Guide p.8) questions and the answers: which head, and why.

• Safety test: your ‘Safety test’ (Day Guide p.8) request and what Team Manager said.

• Findings (recorder): what it got right or wrong, and where it stopped to ask.

Learn 10:40-11:00: everyone fills in the CRAFT Prompt Builder for their head bot (List Tidier worked example). One clear verb in Action; safety line 'Never ... without asking me'; end with 'Remember this.'

Build 11:00-11:25:
• Builders: add your worksheet points to the setup prompt on your card.
• Testers: peer-review with the Y/N checklist and give one suggestion.
• Driver: New Bot (+, or Cmd+N on Mac / Ctrl+N on Windows), exact name, paste setup prompt.

Front Office Team (Client Helper Builder, then Marketing Helper Builder): Client Helper (‘Set up the Client Helper’ (Day Guide p.10)), Marketing Helper (‘Set up the Marketing Helper’ (Day Guide p.10)) - 'Front Office'.

Debrief 11:25-11:30: instructions and memory.

Prompts: Day Guide pages 8-9.

Post back: a photo of one filled-in worksheet and the ‘Memory check’ (Day Guide p.11) answers.

Front Office Team (Client Helper Builder, then Marketing Helper Builder, then Team Manager Builder):
• Client Helper Builder: attach enquiry-1.txt and enquiry-2.txt (drag into the chat or use the attach button). Client Helper - ‘Book 2 client meetings’ (Day Guide p.14) (2 meetings), ‘Draft a reply to an enquiry’ (Day Guide p.14) per enquiry, ‘Improve the reply draft’ (Day Guide p.14). Drafts only, nothing sent. A Connect or Sign-in box for the calendar? Don't click: raise your hand.
• Client Helper Tester: ‘Check the calendar’ (Day Guide p.14) check meetings, ‘Fix a wrong detail’ (Day Guide p.14) fix one wrong detail, ‘Check the reply draft’ (Day Guide p.14) check drafts.
• Marketing Helper Builder: create Poster Maker (‘Set up the Poster Maker’ (Day Guide p.14), 'Front Office'), then ‘Hand off the poster’ (Day Guide p.14) in Marketing Helper's chat.
• Marketing Helper Builder plan B: no poster after 3 minutes, or the bot says it can't make images? Tell the trainer and send ‘Plan B: poster layout’ (Day Guide p.14) in Poster Maker's chat (a poster layout instead).
• Marketing Helper Tester: review with ‘Review the poster and video’ (Day Guide p.15).
• Team Manager Builder: ‘Improve the task list’ (Day Guide p.15) improves the task list; agree the 9am digest content with Team Manager Tester.

Pop-up, captcha or login page? Stop, don't click, raise your hand. The trainer handles it. Never type a password for a real account.

Prompts: Day Guide pages 10-12.

Post back: screenshots of your outputs below.

Goal: one promo video, a 9am digest with voice briefing, and a bot-to-bot hand-off.

Front Office Team (Marketing Helper Builder, then Team Manager Builder, then Team Manager Tester):
• Marketing Helper Builder: ‘Change the poster once’ (Day Guide p.18) poster changes (one round), create Video Maker (‘Set up the Video Maker’ (Day Guide p.18), 'Front Office'), then after Marketing Helper Tester's OK send ‘Hand off one video’ (Day Guide p.18) for ONE video.
• Marketing Helper Builder plan B: video fails, or not ready after 5 minutes? Tell the trainer and send ‘Plan B: video storyboard’ (Day Guide p.18): a 3-frame storyboard and a 3-line script.
• Marketing Helper Tester: reviews with ‘Review the poster and video’ (Day Guide p.15).
• Team Manager Builder: tell the trainer first, then ‘Set up the 9am digest’ (Day Guide p.19) sets up the 9am digest routine.
• Team Manager Tester: ‘Play the voice briefing’ (Day Guide p.19) voice briefing - play it to the room.
• Team Manager Builder + Event Planner Builder: hand-off test ‘Hand-off test to the Event Planner’ (Day Guide p.19); Event Planner Tester finds the job with ‘Check the to-do list’ (Day Guide p.14).

Pop-up, captcha or login page? Stop, don't click, raise your hand. The trainer handles it. Never type a password for a real account.

Prompts: Day Guide pages 13-16.

Never: no payment, no card details, no fog machine without an OK.

Post back: outputs below.

Sheet: [Chris to add 'Lumen Supply Quotes' link]

• Quotes: screenshot of the 'Lumen Supply Quotes' tab with the 3 cheapest quotes for your item.

• Choice: which option you picked, and one line on why.

• Cart: screenshot of the cart with only your pick, stopped before payment (nothing paid, no card details).

• Report: the weekly event status report, numbers checked by Event Planner Tester.

Slots:
• 14:45 Team Manager Tester at Back Office Team (Event Planner Builder types) · Event Planner Tester at Front Office Team (Team Manager Builder types)
• 14:55 Client Helper Tester at Back Office Team (Shopping Helper Builder types) · Shopping Helper Tester at Front Office Team (Client Helper Builder types)
• 15:05 Marketing Helper Tester at Back Office Team (Event Planner Builder types, Money Helper Builder and Tester guides) · Front Office Team builders fix with ‘Fix it after a test’ (Day Guide p.22)
• 15:15 Money Helper Builder and Tester at Front Office Team (Marketing Helper Builder types) · Back Office Team builders fix with ‘Fix it after a test’
• 15:25 re-run failed tests at home

For each bot:
1. Memory check: 'What is your job and what must you never do?'
2. Normal input (a prompt from its card).
3. Incomplete input (leave out a detail, e.g. no date or budget).
4. Wrong input (e.g. wrong date, price over budget).
5. Two trick-it tests from the bank (Day Guide pp.17-19). A good bot stops and asks.

Builders: for each error, describe it with ‘Fix it after a test’, guide the fix, re-run the test.

Not visiting right now? Fix your own bots with ‘Fix it after a test’, or build your own (trial account post).

Post back: your completed test checklists.

1. Next-hire briefs (don't create the bots today): Client Helper Builder Lead Qualifier (‘Job brief: Lead Qualifier’ (Day Guide p.25)), Marketing Helper Builder Guest Concierge (‘Job brief: Guest Concierge’ (Day Guide p.25), in Team Manager's chat). Read each aloud.
2. Each pair: send ‘Write the user guide’ (Day Guide p.25) for a short user guide with known limits from Module 4 (14:45).
3. Front Office Team: fill in the next-step plan (Day Guide p.24): owner, approvals, prototype (today's practice version) vs production (the real one a company relies on).
4. Marketing Helper Tester: collect one thing that worked, one thing a tester caught, one next step from each pair. Marketing Helper Tester and Event Planner Tester present the demos at 16:15.

Prompts: Day Guide pages 20-21.

• One thing that worked
• One thing a tester caught
• One next step

Then a debrief: prototype versus production.

Order of groups: to be confirmed by the trainer.

1. Job brief in CRAFT (p.19)
2. Test checklist (p.20)
3. Next-step plan (p.21)

Builders and trainer: stop routines, empty the shopping cart, remove test meetings, delete unsent drafts.

09:45-09:55 - start now, no waiting:
• Event Planner Tester reads the whiteboard tasks out (photo, Backup Whiteboard or launch-notes.docx); Event Planner Builder types them into Back Office Team's Module 1 (09:45) post below.
• Shopping Helper Builder writes 2 questions, Money Helper Builder and Tester writes 1: copy ‘Ask the Team Manager a question’ (Day Guide p.8) and change only the [task] part.
• Shopping Helper Tester writes the safety test with ‘Safety test’ (Day Guide p.8) ('try to make it say no').

About 09:55 - Driver Event Planner Builder, on Back Office Team's laptop (same shared login): open Team Manager and start a new chat - don't create a second one. Paste the task list with ‘Turn the whiteboard photo into a task list’ (Day Guide p.7). Then type Shopping Helper Builder's and Money Helper Builder and Tester's questions and Shopping Helper Tester's test, one at a time. Team Manager not there by 10:00? Tell the trainer.
If two sessions don't work: Event Planner Builder types in a separate Team Manager chat on Team Manager Builder's laptop.

Jobs:
• Event Planner Tester - Scribe, then Recorder: check every task made it into the list, then post the findings: what it got right or wrong, and where it stopped to ask.
• Shopping Helper Tester: record the answer to your safety test.
• Money Helper Builder and Tester - Org-chart tester: for each task it routes, mark on the org chart whether it went to the right head.

CRAFT in one line: Context (background) · Role (who the bot is) · Action (the job, one verb) · Format (what the answer looks like) · Tone (style) · ! Never ... without asking me. In Module 1 (09:45), just copy ‘Ask the Team Manager a question’ and change only the [task] part.

Pop-up, captcha or login page? Stop, don't click, raise your hand. The trainer handles it. Never type a password for a real account.

Optional: swap the typing seat every 5 minutes.

After debrief: click the bot's name to see its details.

Prompts: Day Guide pages 6-7 / your role card. New words: Day Guide page 5.

Post back: your task list, questions + answers, the safety test result and the org-chart check.

Learn 10:40-11:00: everyone fills in the CRAFT Prompt Builder for their head bot (List Tidier worked example). One clear verb in Action; safety line 'Never ... without asking me'; end with 'Remember this.'

Build 11:00-11:25:
• Builders: add your worksheet points to the setup prompt on your card.
• Testers: peer-review with the Y/N checklist and give one suggestion (Shopping Helper Tester also reviews Money Helper Builder and Tester's).
• Driver: New Bot (+, or Cmd+N on Mac / Ctrl+N on Windows), exact name, paste setup prompt.

Back Office Team: Event Planner (‘Set up the Event Planner’ (Day Guide p.10)), Shopping Helper (‘Set up the Shopping Helper’ (Day Guide p.10)), Money Helper (‘Set up the Money Helper’ (Day Guide p.11)) - 'Back Office'.
• Testers and Money Helper Builder and Tester for Money Helper: send memory check ‘Memory check’ (Day Guide p.11).

Debrief 11:25-11:30: instructions and memory.

Prompts: Day Guide pages 8-9.

Post back: a photo of one filled-in worksheet and the ‘Memory check’ answers.

Back Office Team (Event Planner Builder drives, Event Planner Tester checks):
• Event Planner Builder: create List Tidier (‘Set up the List Tidier’ (Day Guide p.13)) and To-Do List Keeper (‘Set up the To-Do List Keeper’ (Day Guide p.13)) in 'Back Office'. Attach messy-guest-list.xlsx and messy-vendor-list.xlsx (Desktop folder 'Lumen sample data'; drag into the chat or use the attach button), then send hand-off ‘Hand off the lists and to-do list’ (Day Guide p.13) in Event Planner's chat; fix with ‘Fix what the tester found’ (Day Guide p.13).
• Event Planner Tester: ‘Check the cleanup’ (Day Guide p.14) check the cleanup (3 rows by eye), ‘Check the to-do list’ (Day Guide p.14) tracker check, ‘Test days overdue’ (Day Guide p.14) days-overdue test.

Off the driver laptop (own phone or laptop browser, no login, no buying):
• Shopping Helper Builder - price scout: look up your 'In-class pick - Back Office Team' item on Lazada.sg and Shopee.sg. Write the cheapest price, delivery cost and link for each.
• Shopping Helper Tester - price scout: the same item on Amazon.sg. Then write your after-lunch checks: price, delivery, total, rating, link; only our pick in the cart; stopped before payment.
• Money Helper Builder and Tester: open event-budget.xlsx (own laptop, or paper from the trainer) and add up total budget, total spend and money left. Sketch the one-page weekly report: headings, the 3 numbers, risks, next steps.

Your notes are the answer key for after lunch.

Pop-up, captcha or login page? Stop, don't click, raise your hand. The trainer handles it. Never type a password for a real account.

Prompts: Day Guide pages 10-12.

Post back: screenshots of your outputs and your price-scout notes below.

Goal: 3 supply quotes in a Google Sheet with a cart that stops before payment, a reusable report skill, and a bot-to-bot hand-off.

Sheet: 'Lumen Supply Quotes' - [Chris to add 'Lumen Supply Quotes' link]

Back Office Team (Shopping Helper Builder, then Money Helper Builder and Tester):
• Shopping Helper Builder: create Price Checker (‘Set up the Price Checker’ (Day Guide p.18), 'Back Office').
• Shopping Helper Builder: in Shopping Helper's chat, send ‘Find 3 quotes’ (Day Guide p.18) for one 'In-class pick - Back Office Team' item from supply-list.xlsx.
• Price Checker: opens Lazada.sg, Shopee.sg and Amazon.sg while you watch, finds the 3 cheapest quotes and writes them to the sheet. Then it stops.
• Back Office Team: open the sheet, compare the 3 quotes with Shopping Helper Builder's and Shopping Helper Tester's price-scout notes and agree on one.
• Shopping Helper Builder: send ‘Add our pick to the cart’ (Day Guide p.18) with your choice. The bot adds only that option to the cart and stops before payment.
• Shopping Helper Tester: ‘Check the quotes’ (Day Guide p.18) check the quotes, ‘Confirm it never paid’ (Day Guide p.18) confirm nothing was paid, ‘Budget check’ (Day Guide p.18) budget check.
• Time left? Repeat for a second pick item.
• Money Helper Builder and Tester: create Weekly Update Writer (‘Set up the Weekly Update Writer’ (Day Guide p.19), saves skill 'weekly event status report'), attach event-budget.xlsx, send ‘Write the first weekly update’ (Day Guide p.19), then ‘Update the skill’ (Day Guide p.19).
• Event Planner Tester: ‘Check the report numbers’ (Day Guide p.19) (compare with Money Helper Builder and Tester's hand totals), ‘Fix a number’ (Day Guide p.19) fix any mistake, ‘Run the report on new data’ (Day Guide p.19) re-run after one tracker change.
• Event Planner Builder + Team Manager Builder: hand-off test ‘Hand-off test to the Event Planner’ (Day Guide p.19); Event Planner Tester finds the job with ‘Check the to-do list’ (Day Guide p.14).

Captcha ('I'm not a robot'), login page or Sign-in box? Stop, don't type anything, raise your hand. The trainer handles it.

Prompts: Day Guide pages 13-16.

Never: no payment, no card details, no fog machine without an OK.

Post back: outputs below.

1. Next-hire briefs (don't create the bots today): Shopping Helper Builder Venue Scout (‘Job brief: Venue Scout’ (Day Guide p.25)), Money Helper Builder and Tester Invoice Clerk (‘Job brief: Invoice Clerk’ (Day Guide p.25)). Read each aloud.
2. Each pair (and Money Helper Builder and Tester for Money Helper): send ‘Write the user guide’ (Day Guide p.25) for a short user guide with known limits from Module 4 (14:45).
3. Shopping Helper Tester: safety review ‘Safety review’ (Day Guide p.25) to each Back Office bot.
4. Back Office Team: fill in the next-step plan (Day Guide p.24): owner, approvals, prototype (today's practice version) vs production (the real one a company relies on).
5. Event Planner Tester: collect one thing that worked, one thing a tester caught, one next step from each pair. Event Planner Tester and Marketing Helper Tester present the demos at 16:15.

Prompts: Day Guide pages 20-21.

• Bot (AI agent): an AI helper that does a job for you, step by step, and asks before risky steps
• Prompt: the message you type to the bot
• Setup prompt: the first message to a new bot: its job and its rules
• CRAFT: 5 boxes for a clear message: Context, Role, Action, Format, Tone, plus a safety line
• Hand-off: one bot passing a job to another bot by its exact name
• Safety test: ask the bot to do something it should refuse or check with you first
• Connect / sign-in box: a pop-up asking to link an app or log in. Don't click: raise your hand
• Skill: a saved recipe the bot can repeat the same way
• Routine: a job the bot does by itself at a set time, like an alarm
• Page: a live web page the bot makes and keeps up to date
• Memory / 'Remember this.': tells the bot to keep this for next time
• Browser control: the bot opens websites and clicks for you while you watch
• Grok Imagine: the picture and video maker the bot uses
• Prototype vs production: today's practice version vs the real one a company relies on

CRAFT in one line: Context · Role · Action · Format · Tone · ! Never ... without asking me.

Attach a file: drag it from the Desktop folder 'Lumen sample data' into the chat box, or click the attach button and pick it.

Free trial: a usage credit you can use within 7 days. It does not turn into a paid plan by itself. One big task can use all the credit, so keep tasks small.

1. Open https://cursor.com/bot/onboarding?product=grok-bot
2. Choose 'Create an account' (Grok Bot uses a Cursor account).
3. Use a new personal account with your personal email (not a work or client account).
4. If asked for a card, stop and tell the trainer.
5. Find the module you're in on this Padlet.
6. Copy that module's task: create the same bot, with the same name and setup prompt.
7. Use only the fictional Huat sample data (Class Materials). No real names or logins.

No card needed. If it asks for a card, stop and tell the trainer.
8. Pop-up, captcha or login page? Stop and raise your hand.

Full steps: Day Guide page 5, 'Build your own (trial account)'.

Output: the Gmail account is connected for Calendar and Sheets (Gmail optional).

Done when:

(1) the account exists,

(2) the bot on laptop 1 lists the account's Calendar,

(3) the paper checklist is ticked. 

Jobs:

Laptop 1: Types on the projector

Laptop 2: Picks the name and password (trainer card)

Laptop 3: Reads out what Google asks

Laptop 4: Phone verification (one volunteer's phone)

Laptop 5: Records progress and errors Phone verification uses one volunteer's phone.

Steps: https://metaskills-ops-tools-workshop.pages.dev

Expected outputs:

Shopping Helper bot

CRAFT prompt

Supply list with quantities

'Huat Supply Quotes [Laptop 4]' Sheet (3 quotes)

Launch website for Huat Ah Prestige (live link or Page)

Safety card

Next-hire brief

Padlet post

Add a screenshot or link for each output.

No passwords or real personal data.

Title each post: Laptop N - your name - bonus name.

Expected outputs, one per post:

Laptop 1 Builder: thank-you email routine (saved routine + 1 sample draft)

Laptop 1 Tester: lo hei toast script (English and Mandarin)

Laptop 2 Builder: enquiry auto-reply draft for enquiry-2.txt

Laptop 2 Tester: guest FAQ Page (10 FAQs)

Laptop 3 Builder: Hokkien or Singlish voiceover clip (about 20 seconds)

Laptop 3 Tester: 'Why Huat Ah Prestige?' infographic

Laptop 3 either: CNY greeting card image

Laptop 4 Builder: CNY greeting card image (red and gold)

Laptop 4 Tester: influencer caption pack (5 captions)

Laptop 5 Event Planner Builder: 5 RSVP reminder drafts + 1 test sent to the class inbox

Laptop 5 Event Planner Tester: lucky draw (3 winners + 3 messages)

Laptop 5 Money Helper: budget infographic

Add a screenshot or link. No passwords or real personal data.

Instructions: your role page on the class website.