The Monday Briefing That Runs Without You
The full series
- The Prompt Is the Least Important Part
- Three Files That Replace a Chief of Staff
- You Don't Have a Productivity Problem. You Have a Setup Problem.
- Stop Telling AI What to Do. Tell It What Done Looks Like.
- The _MANIFEST.md: Five Minutes That Save Hours
- Plugins Are Composable. Stack Them.
- The Monday Briefing That Runs Without You (you are here)
- Custom Skills: Build Once, Run Forever
- AI as a Team, Not a Chatbot
- Cowork Is Not Chat. Stop Using It Like Chat.
Every Monday at 7 AM, Claude checks Slack channels, scans the calendar, flags what needs prep, and saves a briefing to a folder. Nobody typed a prompt. Nobody opened the app. The work ran on its own.
There is a version of Monday morning already in place for the people who set this up. Your laptop opens, and a briefing folder contains a new file. The file contains every meeting on your calendar for the week, every Slack thread that needs a response, and every deadline approaching in the next five days, organized by priority and flagged by urgency. It was saved during the hours when you were asleep.
No prompt was typed. No session was opened. The system ran on schedule, with full context loaded from the same files that power every manual session.
You were asleep. The work was done.
From tool to system
Everything in this series so far has required someone to sit down and start a session. Open Cowork, type a task, and receive the output. Your context files are compound. Your plugins stack. Your delegation patterns sharpen.
But every workflow still begins the same way, with a person telling Claude what to do.
Scheduled tasks remove that starting trigger entirely.
The /schedule command in Cowork sets a task to run automatically on a recurring cadence, whether daily, weekly, or monthly. Define the task once, set the timing, and Cowork handles execution from that point forward, requiring no manual input, no prompt, and no one present at the keyboard.
This is the difference between a tool and a system. A tool waits for input. A system delivers output on its own schedule.
Not a chatbot. A system.
How /schedule works
Type /schedule in any Cowork session, and Claude walks through the setup. The process covers what the task does, when it runs, and where the output goes. Every scheduled task inherits your Global Instructions, your connected tools, and your context files automatically, so it doesn't start cold.
That inheritance changes everything about what scheduled tasks can produce.
The Monday briefing already knows your current priorities because your about-me file lists them.
The Friday status report already uses the right format because your working-preferences file specifies it.
The daily competitor scan already filters for relevance because your context architecture defines what matters.
Everything you built in earlier weeks now powers tasks that run on their own.
Three starter automations cover the workflows that consume the most recurring time in knowledge work, and the exact prompts to use are listed below.
Three automations worth setting today
The Monday morning briefing
Every Monday at 7 AM, this task runs the following prompt: "Check Slack channels and calendar for the week. Summarize what's coming up, flag anything that needs prep, and save a briefing to /weekly-briefings."
This single automation replaces the 30 to 45 minutes most knowledge workers spend on Monday morning sorting through what happened over the weekend and scanning the week ahead for deadlines, meetings, and open threads. The briefing lands in the folder before the alarm goes off.
The Friday status report
Every Friday at 4 PM, this task runs the following prompt: "Pull completed tasks from Asana, summarize what shipped this week, draft a status update, and save to /reports."
We've seen status reports take between 20 and 45 minutes every Friday afternoon for professionals who compile their weekly output manually. The scheduled task pulls the raw data, writes the narrative summary, and saves the file while the workday winds down on its own terms.
The daily competitor scan
Every day at 9 AM, this task runs the following prompt: "Research [competitor names] for news, product updates, or pricing changes. Save a summary only if there is something new."
The conditional clause at the end is the critical design choice. No news produces no file. The briefing folder doesn't accumulate empty reports that waste attention on mornings when nothing has changed. When a competitor ships a pricing change or announces a product update, the summary appears that same morning, without anyone remembering to search for it.
Schedule plus connectors
Scheduled tasks produce value on their own, but they reach full potential when combined with connectors that pull live data from the business tools that already hold the information.
Connect Slack and your calendar, and the Monday briefing draws from both data sources without any additional configuration. Connect Gmail, and a morning task can scan your inbox for invoices, extract amounts and vendor names, and update a spreadsheet in your local folder. Connect Google Drive, and a weekly task can pull all comments from a shared strategy document, categorize them by theme, and save the categorized digest.
The pattern scales because each connector adds a new data source that every scheduled task can access without further setup or repeated authentication.
Automate the Monday briefing that takes 30 minutes of sorting every week.
Automate the Friday status report that nobody enjoys writing and that everyone keeps postponing.
Automate the competitor tracking that matters strategically but never gets prioritized above client work.
Automate the invoice processing that sits untouched in an inbox until month-end creates urgency.
Each of these automations stacks on the infrastructure already in place. Context files provide identity and voice.
Connectors provide live data.
The schedule provides the trigger.
Nobody provides anything at the moment of execution, because the system already has everything it needs.
The limitation is worth knowing
Scheduled tasks run only when the computer is awake, and Claude Desktop is open. If the machine is asleep at the scheduled time, Cowork catches up on return. But if the app is closed entirely, the task doesn't execute at all.
The workaround takes five seconds.
Don't close Claude Desktop. Put the computer to sleep instead, because the session survives sleep without issue. On Sunday night, leave the app running, and the Monday 7 AM briefing fires on schedule.
This constraint won't last forever, and cloud-based scheduling is the obvious next evolution. For now, the trade-off is a laptop that sleeps rather than shuts down, and an app that stays open quietly in the background. We've seen practitioners accept this cost without hesitation, because the return is work that runs on its own clock, on its own schedule, without human involvement.
The shift underneath
There is a moment when Cowork stops being something a person uses and starts being something a person runs. The transition happens the first time a scheduled task delivers output that nobody requested, on a morning when nobody sat down to begin a session.
We've seen this shift consistently across practitioners who set up even one recurring automation.
The relationship with the tool changes afterward. Cowork stops looking like an assistant waiting for instructions and starts looking like a system that generates output on its own schedule, with context already loaded, voice already matched, and priorities already ranked.
The briefing knows your calendar because the connector pulls live data.
The briefing uses your format because the preferences file specifies it.
The briefing flags what matters because your about-me file defines current priorities with enough specificity for the system to rank by relevance.
All of that context was built over previous weeks. Now the system runs on its own.
The prompt was the least important part. Turns out, presence was optional too.
Do This Today
- Type
/schedulein a Cowork session and explore the setup flow. - Set up a Monday 7 AM briefing with this exact prompt: "Check Slack channels and calendar for the week. Summarize what's coming up, flag anything that needs prep, and save a briefing to /weekly-briefings."
- Connect your calendar if you haven't already (Settings > Connectors).
- Leave Claude Desktop open overnight Sunday. Put your computer to sleep instead of shutting it down or closing the app.
- Monday morning, open your laptop and check the /weekly-briefings folder. The briefing is already there.
---
Next in the series: a skill file is a markdown document that encodes everything you would normally spend twenty minutes explaining. Purpose, inputs, process, output, constraints. Write it once. Never explain the workflow again.