This lesson is being recorded

Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.

Bruno AshfordBruno Ashford @brunoashfordSubscribe

Module 10 · Lesson 10.5 · 13 min

The Owner's Morning Brief

Build a daily automatic summary of what needs your attention: emails, sales, cash and pending tasks, ready before you start work.

Module 10
Agents That Work While You Sleep

Schedules, headless runs, hooks and one-word commands

Bruno Ashford
Bruno Ashford · Module 1001 / 12
The problem
A routine that depends on your memory is not a routine.
Bruno Ashford
Bruno Ashford · Module 1002 / 12
Lesson 10.1

Three ways to schedule

OptionRuns whereBest when
Cloud routine (/schedule)Anthropic cloudLaptop closed, sources are connectors or GitHub
Desktop scheduled taskYour computerYou use the Claude desktop app
launchd, cron, Task SchedulerYour computerFiles live locally, full control

Cloud routines are a research preview; check your plan's limits.

Bruno Ashford · Module 1003 / 12
Lesson 10.2

Headless, in one line

claude -p runs the work without the conversation.

  • Nobody is there to approve
  • Decide permissions in advance
  • dontAsk plus a short allowlist
  • Redirect output to a dated file
Bruno Ashford · Module 1004 / 12
Lesson 10.2

Safe defaults for unattended runs

  1. 1Read onlyStart with the Read tool
  2. 2dontAskAnything else is denied
  3. 3Right folderLoads your CLAUDE.md
  4. 4Never skip checksOnly in isolated containers
Bruno Ashford · Module 1005 / 12
Lesson 10.3
Instructions guide the agent. Hooks enforce the rules.
Bruno Ashford
Bruno Ashford · Module 1006 / 12
Lesson 10.3

Hooks you will actually use

EventWhen it runsUse it to
PreToolUseBefore an actionBlock risky commands
PostToolUseAfter an actionKeep an audit log
NotificationWhen Claude needs youGet a desktop alert
StopWhen Claude finishesRun a final check
Bruno Ashford · Module 1007 / 12
Lesson 10.4

One word, same result

Commands and skills are now the same thing.

  • Name becomes the slash command
  • $ARGUMENTS passes in the details
  • Manual-only for client-facing work
  • Share the .claude folder
Bruno Ashford · Module 1008 / 12
Lesson 10.5

The morning brief

  1. 1Yesterday in numbersSales, leads, cash
  2. 2RisksOverdue and at risk
  3. 3Needs youMessages only you can answer
  4. 4TodayMeetings and top three priorities
Bruno Ashford · Module 1009 / 12
Illustrative example, not research

One partner's mornings

50 to 12minutes to get oriented
6:45ambrief ready
1missed deadline caught in week one
Bruno Ashford · Module 1010 / 12
Project

Seven days in production

Trust is built with evidence, not hope.

  • One routine, scheduled
  • Hooks tested and firing
  • One log line per run
  • Improve the prompt on day seven
Bruno Ashford · Module 1011 / 12
Recap
The best automation is the work you find already done, checked and logged when you sit down.
Bruno Ashford
Bruno Ashford · Module 1012 / 12
01 / 12

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

1Decide what goes in the brief

Keep it to one screen. A good default: yesterday's numbers (sales, leads, cash), anything overdue, emails that need you personally, today's meetings with context, and the top three priorities. Everything else waits.

Prompt for Claude
Help me design my morning brief. Ask me what I need to know each morning to run the business, then write a one-page prompt file at prompts/morning-brief.md. Sections: yesterday in numbers, risks and overdue items, messages that need me personally, today's meetings with one line of context each, and my top three priorities. Maximum 300 words of output.
2Connect the sources

Start with files you already export (CRM, aging report, ops check). Add your email and calendar through a connector or MCP server from Module 6 when you are ready. For unattended runs, allow only the read tools of each connector; check the exact tool names with /mcp.

Prompt for Claude
/mcp
3Test the brief headless

Run it by hand exactly as the scheduler will, and read the result critically. If a section is vague, fix the prompt file, not the output.

Terminal
claude -p "$(cat prompts/morning-brief.md)" --permission-mode dontAsk --allowedTools "Read" > "briefs/brief-$(date +%F).md"
4Schedule it for weekdays

Use the option you chose in lesson 10.1. On a Mac, the recipes file has a launchd example set to 6:45am on weekdays. On Windows, create a task with /sc weekly and the five weekdays. A cloud routine works too if your sources are connectors.

Terminal
schtasks /create /tn "AI Morning Brief" /tr "powershell.exe -NoProfile -ExecutionPolicy Bypass -File C:\ai\morning-brief.ps1" /sc weekly /d MON,TUE,WED,THU,FRI /st 06:45
5Run it for seven days and log the results

Each day, add one line to the Routine Run Log: did it run, how long you saved, was anything wrong or missing. At the end of the week, ask Claude to review the log and the briefs and suggest improvements.

Prompt for Claude
Read logs/routine-run-log.csv and the last seven files in briefs/. Tell me: how many runs succeeded, total minutes saved, which sections I never used, and three changes to prompts/morning-brief.md that would make it more useful.

Most owners start the day by opening email and reacting to whoever shouted loudest overnight. By 10am the important thing has been pushed aside by the urgent thing. The morning brief flips that: before you open anything, one page tells you what changed, what is at risk and the three things only you can do today.

This lesson puts together everything from the module. A prompt file, a headless run with tight permissions, a schedule, a hook that logs it, and a run log that proves its value. After seven days you will not want to start a day without it.

Key points

  • Start the day on your priorities, not on your inbox.
  • One screen, five sections, three priorities.
  • Unattended runs get read-only access to email and calendar.
  • Seven days of logs tell you what to keep and what to cut.

Avoid

  • Building a brief so long you stop reading it by day three.
  • Giving the brief permission to send or reply to emails.
  • Skipping the run log, then having no proof it saved time.
  • Never updating the prompt after the first week.
Real-world example: a law firm

The managing partner of a small US family law firm used to spend the first 50 minutes of each day in her inbox and case management system. Her brief now arrives at 6:45am: new enquiries overnight, filings due in the next five days, unbilled time over two weeks old, and client emails flagged as upset. In the first week it surfaced a filing deadline that had been entered in the wrong matter. Her morning review now takes about 12 minutes, and she starts the day on the work only she can do.

Bruno Ashford Subscribe