The free prompt (copy this now):
You are my Monday morning briefing assistant. Check my calendar for the week ahead. For each meeting or call, give me: who I’m meeting, what they do, one insight about them I can use to open well, and what I likely need to prepare. Then list any emails that need a reply before noon. Keep it under 400 words. Deliver it as a clean briefing document.TL;DR: Cowork Scheduled Tasks lets you write a prompt once and Claude runs it automatically, daily, weekly, on weekdays, or on demand. I’ve set up six recurring tasks that run without me. The one that’s changed my week most is the Monday 4am brief: a full situational read of my week, delivered before I’ve had to think about what is happening this week. This post gives you the exact setup, the refined prompts, and the three things I got wrong before I got it right.
By the end of this post, you’ll have the exact Cowork Scheduled Tasks configuration I use as a working consultant.
Why I Can’t Be the Trigger
Here’s what I tried first. I built a morning briefing inside a regular Claude Project with a system prompt that said something like “you are my assistant, help me plan my week.” I’d open it Monday morning, paste in my calendar, and ask for a read of the week. It worked, sort of. But it meant I had to remember to do it. And Monday mornings, I don’t remember anything before coffee. Especially if we have been beaching all Sunday afternoon.
The constraint that shaped this design is simple: I can’t be the trigger. If I have to initiate the system, I’ll skip it when I most need it which is always the high-pressure week, the one with the difficult client or the back-to-back days. The whole value of a briefing is that it shows up before you’ve started making decisions, not after you’ve already started improvising.
What shifted the design was looking at how I actually use Mondays. The first 40 minutes are spent reconstructing context who am I seeing, what do they care about, what do I need to know before I walk in. That work isn’t hard deep thinking. It’s just friction. And friction at the start of a week compounds. Cowork Scheduled Tasks removes the friction entirely. The brief is there when I wake up. I read it over breakfast. I arrive at every conversation already ahead.
The Minimum Viable Brief (Free Version)
The minimum viable version is genuinely simple. Open Cowork Desktop. Start a session. Type /schedule. Claude asks you three questions. You answer them. Done.
The prompt you need for a basic Monday brief:
Check my calendar for the coming week. List every meeting or commitment with the name of the person I’m meeting, their role if you can identify it, and what I need to do or know before I walk in. Then check my email for anything that requires a reply today. Format this as a weekly briefing, not a conversation. Keep it under 500 words.
That’s the free version. It works. Claude connects to your calendar and email (once you’ve enabled those connectors), runs the check, and produces a briefing you can actually read in under three minutes.
To get the production-grade version, the one that researches your interviewees, generates podcast angles from your book, and adapts each week based on who’s in your calendar, please consider becoming a paid member.
The Production Brief (Five-Module System)
Here’s the production-grade prompt I run every morning (Monday to Saturday) at 4am. This is the version that took a few weeks to refine.
The 4am Brief — Production Prompt:
You are my morning briefing assistant. Run this task automatically
every Monday to Saturday at 4:00 AM.
STEP 1 — CALENDAR SCAN
Check my calendar for the day ahead. For each event or meeting, extract: (a) the name and role of the person I'm meeting, (b) what they do and who they work for, (c) what I likely need to know or prepare before this meeting. Flag any back-to-back sessions where I'll need to transition quickly. Check emails related to the calendar appointment and add any supporting details.
STEP 2 — EMAIL TRIAGE
Check my email for any messages received in the last 48 hours that require
a reply before noon Monday. List the sender, subject, and one sentence
describing what action is needed. Do not summarise every email — only the
ones that need a response. Check that I don't have any emails that I haven't replied to yet.
STEP 3 — INTERVIEW RESEARCH
For any person appearing in my calendar this week whom I have not met before
(identify this from calendar history), provide a deep search for: their LinkedIn or public
professional profile, one recent article, post, or project they've been involved in, and one insight or observation I can use to open the conversation well.
STEP 4 — PODCAST ANGLES
Check my calendar for any podcasts upcoming today. For each relevant podcast, generate three specific talking point angles that connect their work to the themes in my book AI for Purpose - I am focusing on AI Blueprints (Workflows and Human in the loop). Make these specific and usable — not generic "great conversation topics" but actual angles I could open with
in the first five minutes.
STEP 5 — BRIEFING FORMAT
Assemble all of the above into a single clean document with these sections:
— Today at a Glance (3–5 bullet summary)
— Priorities (email replies needed before noon)
— Meeting Briefings (one block per meeting, in calendar order)
— Podcast Prep (if applicable)
- Other things that might need attention (Emails not replied to etc, people asking questions)
The document can be as long as required, I prefer to be prepared, and the more I am aware about the week ahead, the less noise I have.Section 4: The Build Walk-Through
Build It Now: Three Steps, Fifteen Minutes
Step 1: Connect Your Apps
What you’re doing: Giving Claude the data sources it needs before you write a single word of prompt.
Do this now: Open Cowork Desktop. Go to Settings → Connectors. Connect Google Calendar (or your calendar of choice) and Gmail. If you use a different email client, connect that instead. Test each connection by typing a quick task: “What’s on my calendar this week?” If Claude returns real data, you’re connected.
What you should see: A list of your actual calendar events for the current week, with names and times.
The asset: This setup takes four minutes. Do it before you write any prompts — a scheduled task with no connected data sources just returns empty or hallucinated output, which is worse than useless.
If you’re new to this: Start with Calendar only. Email adds complexity. Get the calendar brief working first, then add email triage in week two.
If you’ve done this before: Add Notion or Drive as a third connector if you keep client notes there. Claude can cross-reference a meeting guest against your existing client notes and flag anything relevant before you arrive.
Why this works: Scheduled tasks run without you watching them. That means if the connectors aren’t established before the task runs, Claude has no way to prompt you for them mid-task. Connections have to be solid before you schedule anything.
Step 2: Write the Prompt in Sections
What you’re doing: Structuring the brief so each section has a distinct instruction Claude can follow independently.
Do this now: Copy the production prompt from Section 3. Open it in a text editor. Personalise the two placeholders: [INSERT PODCAST NAME] and [INSERT BOOK TITLE / KEY THEMES]. For the book themes, give Claude three to five words or phrases that capture what your book is actually about — “future of work, AI and agency, human-centred leadership” is better than a subtitle.
What you should see: When you run this prompt manually (before scheduling it), you should get a document with five clearly separated sections and content under each one that’s specific to your actual week.
The asset: The prompt block above. Copy it. Use it directly. Don’t rewrite it from scratch, use the structure and modify only the personalised fields.
If you’re new to this: Run the prompt manually on a Tuesday or Wednesday — midweek, when your calendar is full — rather than scheduling it blind. You’ll see immediately what’s working and what needs adjusting before you trust it to run unsupervised.
If you’ve done this before: Add a sixth step to the prompt asking Claude to flag anything in your week that conflicts with a stated priority. Give it your top three priorities for the quarter as part of the prompt context.
Why this works: A single long instruction tends to produce long, unfocused output. Breaking the prompt into labelled steps (STEP 1, STEP 2, etc.) tells Claude to treat each one as a distinct task. The result is a modular document where each section is independently useful, not a wall of text you have to skim.
Step 3: Schedule It
What you’re doing: Setting the task to run automatically, weekly, at a time when it’s useful rather than disruptive.
Do this now: In Cowork, type /schedule at the start of a new session. When Claude asks for the prompt, paste in your refined version from Step 2. When it asks for the cadence, choose “Weekly — Monday.” When it asks for the time, choose a time between 3:00 AM and 5:00 AM in your timezone. This ensures the brief is ready when you wake up, not still running.
What you should see: A confirmation that your scheduled task is active, with the next run date visible.
The asset: The /schedule command, plus this timing decision — 4:00 AM is the sweet spot. Early enough that the brief is finished by 6:00 AM. Late enough that Monday’s calendar data is accurate.
If you’re new to this: Schedule it for “on demand” first. Run it manually three or four times. When you trust the output, switch to weekly automatic.
If you’ve done this before: Create a second scheduled task that runs Friday at 3:00 PM — a brief end-of-week review of what happened against what was planned. The morning brief and the Friday review together form a closed loop.
Why this works: The timing isn’t arbitrary. Running a brief on Sunday night pulls incomplete calendar data — people often add Monday meetings at the last minute. Running it Monday morning at 4:00 AM catches everything that landed over the weekend, including the late email that changes the week.
What Broke (And What I’d Do Differently)
The first version of this broke because I asked Claude to “research” everyone in my calendar, full stop. If you have twelve meetings in a week, that’s twelve research tasks in a single prompt. The output ballooned to 1,800 words, most of it generic LinkedIn summaries that told me nothing I couldn’t have found in thirty seconds. I’ve since added the constraint “only for people I haven’t met before (identify this from calendar history)” which cuts the research section to two or three people at most, and makes each entry actually worth reading.
What I’d do differently if I were starting today: I’d set up the Friday review task at the same time as the Monday brief. The two tasks are designed to work together, the Friday brief surfaces what I didn’t get to, which seeds the next Monday brief with context I’d otherwise lose over the weekend. I set up the Monday task six weeks before I built the Friday one, and I wasted five weeks of useful context as a result.
What’s still unresolved: the podcast angles section is the weakest part of the system. Claude generates good angles but needs more programming, maybe a skill.
What You’ve Built
You now have a production-grade morning cowork briefing system that runs without you initiating it. It scans your calendar, triages your email, researches new contacts, and generates podcast angles, all before you’ve made your first coffee.
That system is the foundation for a wider automation stack. The next layer is a client update task: a Wednesday prompt that checks your active project folders and emails, then drafts a two-paragraph status update for each active client. You don’t send it automatically, Claude drafts it, you review it in two minutes, you send. The research time drops from twenty minutes per client to ninety seconds.
The variable to adapt is the data source. Right now this runs on Calendar and Gmail. Add Notion, Drive, or Slack as connectors and the brief gets more specific, it can pull your own notes on a client before a meeting, not just their public profile.
Phil