The MSO AI Operator Method
Four steps to turn a folder of context into a Cowork workflow that runs itself — gathering, drafting with you, then building and sending the finished thing on a schedule.
Gather
Drop the templates, data, constraints, and inspiration into a Cowork project or a desktop folder it can read.
Map
Cowork lays the pieces against your constraints so the plan fits real life before committing.
Draft
It posts a plain-text plan and you riff on it together until you approve.
Build
On a schedule, Cowork builds the plan and list, then delivers it your way — emailed or saved to Drive.
01 · Gather a folder
Put the context somewhere Cowork can reach it, two ways work: spin up a new Cowork project, or point Cowork at a plain folder on your desktop you've granted it access to. Use a project when you want a persistent workspace; use a desktop folder when the files already live on your machine. Either way, a few strong files beat a dump of everything. For a weekly meal planner, it might hold:
Inspiration and reality, side by side — the first three teach taste, the last one checks what's actually on hand.
- Inspiration sources. Recipes you actually want to cook from — Ottolenghi pages, your Instant Pot go-tos, the pasta you screenshotted off a friend.
- Past shopping lists. A few weeks' worth, so Cowork learns your real staples and the quantities you actually buy.
- Favorite meals. The dishes that always land, so the plan leans on proven hits instead of a week of experiments.
- A photo of your fridge or pantry.show, don't type Snap the shelves and let Cowork read what you already have, so the plan uses it up before the list buys more.
02 · 03 · Teach it the workflow
Now define how the work should run. Paste the prompt below as the first message in your Cowork project. It looks around the folder, interviews you with smart questions, and writes the standing instructions — your Map → Draft → Build sequence — so every run behaves the same way.
This example is wired for the weekly meal planner. Swap the inputs and it fits any recurring deliverable.
Why interview first. The questions force you and Cowork onto the same page before any instructions get written — so the workflow matches how you actually plan, not a generic guess.
04 · Put Build on autopilot
Once the workflow runs cleanly by hand, hand it the clock. In any Cowork session, type /schedule to turn the prompt into a recurring task. Each run opens a fresh session with access to your project folder and connectors, so it can read the latest fridge photo, check your calendar, and hand you the finished list.
It triggers on its own
No reminder, no opening the app to kick it off. The scheduled task wakes up and starts the run.
Reads the folder and your week
Pulls the template, taste cheat sheet, and latest fridge photo, checks next week's calendar, and maps seven dinners around the busy nights and what's on hand.
Posts ideas and waits
The week's draft is sitting in the thread when you sit down — meals per night, key ingredients, nothing built yet.
You go back and forth
Swap Tuesday's salmon, ask for something faster Wednesday, double a recipe for leftovers. It adjusts until you say go.
Builds it, then asks how to deliver
On your go, it fills the template and writes the aisle-grouped list, then asks whether to email it or drop it in a new Google Doc — and delivers it before you've left for the store.
First, give the task the connectors it reaches through:
Add them once in Claude Desktop → Customize → Connectors (click the +, choose Google Workspace, authorize in the browser), then make sure they're toggled on for this task. The first is always needed; turn on whichever delivery you'll use.
- Google Calendar. Lets the Map step read next week and flag your busy nights. Read access is all it needs.
- Gmail. For the email route — delivers the list to your inbox.
- Google Drive. For the doc route — saves the week's plan and list as a new Google Doc.
The one hard requirement. Scheduled tasks only run while your computer is awake and Claude Desktop is open — so point the cadence at a time you're usually around, or set your machine to wake a few minutes before it fires.
The four kinds of context
Behind that meal-planning example, every strong Gather folder pulls from the same four buckets. Here's how to think about it for any recurring deliverable you want Cowork to run, not just dinner.
Templates
The exact file and format you want filled in, so output matches structure on the first try.
e.g. last week's plan, a shopping-list skeletonReference examples
One or two finished pieces that landed well. Cowork pattern-matches quality from these.
e.g. a week everyone actually lovedPrep and style guide
How things should come together so the output fits your kitchen, not a generic recipe blog.
e.g. cook time limits, batch-prep habitsDecision cheat sheet
What your household cares about and how you prioritize. Fuels the map phase.
e.g. allergies, dislikes, who's pickySource data
The raw inputs that change each cycle — and the connectors Cowork reads them from at run time.
e.g. pantry stock, calendar, budget, fridge photoStanding requests
Specific asks from the people you feed so nothing requested last time gets dropped.
e.g. the kids' meal requests this weekHard constraints
Non-negotiable rules on count, time, or ingredients that the output must always honor.
e.g. exactly seven dinners, no nutsDelivery + cadence
Where the finished thing goes and how often Cowork should run the whole loop.
e.g. email it or save to Drive, every Friday at 4