Claude Code Daily Brief: A 5-Minute Morning Plan

A Claude Code daily brief replaces the worst way to start a day, in your inbox, with a five-minute plan built from your own work: your notes, the follow-ups that are due, the proposals waiting on a reply and the goal you are working toward.

A Claude Code daily brief is a short morning plan an AI agent writes from files you keep: yesterday's notes, follow-ups due, open proposals and your 90-day goal. It gives you three priorities, time blocks and loose ends, and every item points to something real rather than generic advice.

Below is what goes in, the prompt, how to schedule it, and the habit that makes it work.

What the brief reads

The brief is only as good as what it reads. Five inputs cover most businesses:

Keep these as plain files in a Claude Code folder: business.md (with your normal week and your goal), a notes/ folder for daily notes, and the send logs and proposals your other work already produces.

What comes out

One screen, in this order:

1. Top three for the day, picked by your goal first and then by what is actually due.
2. Time blocks that match the kind of day it is.
3. Follow-ups due, each with a pointer to the draft.
4. One content task.
5. Loose ends, including anything to hand to a teammate by name.
6. Carried over, and after three days of carrying the same item: do it today, hand it off or drop it.
7. One line on the goal.

The prompt

Save this as a skill or a command, or just type it each morning:

Read business.md, everything in notes/ from the last two days, the send
logs in outputs/outreach/ and the proposals in outputs/proposals/.
Write today's brief: top 3 (goal first, then what is due), time blocks
for today's type of day, follow-ups due with the path to each draft,
one content task, loose ends, items carried over (flag anything carried
3+ days), and one line on the 90-day goal. Every item must come from a
file; no generic advice. Under 250 words.

If you use it every day, turn it into a skill so /brief runs it. My Claude Code skills examples include a daily brief skill you can copy.

A worked example: a Wednesday brief

Here is what a real brief looks like for the fictional bookkeeping firm in my AI Operator Kit. Sam runs it on a Wednesday morning.

Wednesday 14 October. Client close day, no calls booked.

Top 3
1. Write and send the Hartwell proposal (promised Friday, 5 days late).
   40 min. Run /proposal on the call notes.
2. Send Dana the prep questions for Thursday's call. 10 min.
3. Chase the Morales invoice: 23 days out, and your terms pause work
   at 21 days. 5 min; Rebecca can send the reminder.

Follow-ups due
- Front Range Lawn and Snow, touch 2. Draft ready in outputs/outreach/.

Content
- Reel idea from your notes. Thursday is content day: run /repurpose
  today so the script is ready.

Loose ends
- Rebecca: check the November close schedule.

Goal: 2 of 4 new retainers signed. On track if Hartwell closes.

Look at what it did. It knew Wednesday is a client close day. It put the late proposal first because it was promised and moves the goal. It used Sam's own payment terms rather than a generic "follow up on invoices". It handed a task to a teammate by name. And every item points at the file or command that does the work.

Make it run on its own

Claude Code can schedule the brief so it is waiting when you sit down. Anthropic's scheduling docs describe three options:

For a daily brief that reads your local notes, a desktop scheduled task is the natural fit: set it for a few minutes before you start work. If your notes live in a repository, a cloud routine works even when your computer is off.

The habit that makes it work

The brief does not fix a morning on its own. Two habits do:

• Feed it. Thirty seconds of notes the evening before is the difference between a useful plan and a thin one. A voice memo in the car, transcribed, is fine.
• Do the top three before email. The plan is only useful if it runs your morning, not the other way round.

Give it a week before judging it. The first two or three briefs are only as good as the notes you have started keeping. By the end of the first week it knows your follow-ups, your proposals in flight and what carried over, and the plan starts to feel like it was written by someone who knows your business, because it reads the same files you do.

Daily brief ideas for different roles

• Agency owners: client deliverables due, proposals out, outreach touches due.
• Founders: the one metric that matters this week, decisions waiting on you, people to unblock. My Claude Code for founders post covers the rest of that setup.
• Sales: calls today with a one-page brief each, follow-ups due, deals going quiet.
• Executive assistants: your executive's meetings with a prep line each, the emails that need them and this week's deadlines. The full set is on Claude skills for executive assistants.
• Creators: what to record, what to publish, what to repurpose from last week.

Mistakes to avoid

• Letting it fill gaps with generic advice. "Review your pipeline" is not a task. Tell it every item must come from a file.
• Too many priorities. Three is the limit. Everything else goes in blocks or loose ends.
• Never logging sends. Without send logs it cannot tell which follow-ups are due.
• Reading email first. The brief only works if you do the top three before the inbox.
• Ignoring carried-over items. If something carries for three days, decide: do it, hand it off or drop it.

Make it yours

Adjust the brief to how you work. Add a line for the one number you watch daily (bookings, revenue, leads). Add your calendar if you connect it. Ask for a short end-of-day version too: what got done, what moves to tomorrow, and the note it should read in the morning. Small changes like these make the brief something you trust rather than another report you skim.

Claude Code daily brief: FAQ

Does Claude have a daily brief feature?

Claude does not ship a fixed daily brief, but Claude Code can produce one from your own files, and you can schedule it to run each morning with a desktop scheduled task or a cloud routine.

Can the daily brief read my email and calendar?

Claude can read email and calendar through connectors, such as Google's, when you connect them. Start with read-only access and keep the brief focused on your own notes and logs until you trust it.

How long should a daily brief be?

A daily brief works best under 250 words on one screen. If it gets longer, it turns into another inbox. Cut anything that is not due today or does not move the goal.

What if I miss a day?

Anything unfinished carries forward to the next brief, and items carried for three days get flagged so you decide: do it, hand it off or drop it.

Can I get the daily brief on my phone?

You can run the brief from the Claude app on your phone by pasting in your notes, or have a scheduled task save it somewhere you can open on your phone. Keep the source files on your computer if they contain client details.

How do I schedule a Claude Code task every morning?

Use a desktop scheduled task in the Claude app if the brief needs your local files, or a cloud routine if your notes live in a repository. Set it for a few minutes before you start work.

Get the brief ready-made

The AI Operator Kit includes the /brief command and the Daily Operator Plan, plus the outreach logs, proposals and business files it reads, so the plan is useful from the first morning.