It's Sunday night and I'm replanning the whole week in my head. Again. Who has what, which two things collide on Tuesday, what we're eating, what I still need from the store.

That job is gone now. An agent audits my calendar every week and sends me the rundown like a chief of staff would. Conflicts, whether my week matches my priorities, the weather and what to wear, meals built around the schedule, the grocery list by aisle.

Three steps to build it. Then a set of blocks you paste in to make it yours.

STEP 1 Connect calendar Google or Outlook STEP 2 Context file (.md) priorities, people, meals STEP 3 Schedule the audit weekly, or daily
Connect it, teach it, schedule it. After that, the brief just shows up.

1. Connect your calendar

Claude has to see the real calendar, not a pasted screenshot of it. In your connectors, turn on Google Calendar if that's where your life lives.

If you're an Outlook person, your calendar comes through the Microsoft 365 connector, and that one needs a paid plan. So Pro is the price of entry for Outlook. Worth knowing before you get twenty minutes in and wonder why it won't connect.

Connectors Turn on the calendar your week actually lives in. G Google Calendar Connected M Microsoft 365 (Outlook) Needs Pro plan
Google Calendar connects on any plan. Outlook comes through Microsoft 365, which needs Pro.

2. Write the calendar context file

This is the step that makes the audit worth reading. A calendar is just a list of blocks. The agent can only tell you if your week is good or bad if it knows what good looks like for you.

So you write that down once, in a plain text file on your desktop that Claude can read. Your priorities, the people on the calendar, your location, your favorite meals, your go-to restaurants, what a realistic day looks like. I call mine calendar-context.md.

Don't write it from scratch. Let Claude interview you:

Interview me so you can audit my calendar well. Ask one question at a time. When we're done, save everything to a file on my desktop called calendar-context.md and read it every time you look at my calendar.

The questions the interview should ask

Copy these in if you want to steer it, or just answer as it goes. The better your answers, the sharper the audit.

  • Priorities. What are your top three priorities this quarter? What should your week have more of, and less of?
  • People. Who shows up on your calendar? Kids, partner, team, clients. What are their schedules and their constraints?
  • Boundaries. When does your day start and end? What is sacred: workouts, school pickup, a no-meeting block, bedtime?
  • Location. Where do you live, and where do you commute to? This is what the weather block runs on.
  • Food. Your favorite weeknight meals, the ones the kids will actually eat, your go-to restaurants, any allergies. Mine knows Olive won't eat green things and Luna only wants pasta.
  • Energy. When are you sharpest? When do you crash? What kind of day drains you?
  • Red flags. What does a bad week look like? Back-to-back meetings, no movement, three evening things, nothing with the girls?
Do this quarterly: priorities shift. Every three months, re-run the interview and let it update the file. Then the audit judges your week against what matters now, not what mattered in January.
calendar-context.md # Priorities this quarter - mornings with the girls before 8am - 3 workouts a week, non-negotiable # People - Olive (4): preschool 9 to 1, no green food - Luna (2): naps 1 to 3, pasta only # Location - home: Los Angeles. commute: 25 min # Food, red flags...
One plain file. The agent reads it every time it audits, so it knows what your good week looks like.

3. Schedule the audit

Now the agent. This is a scheduled task: it runs on its own, combs through every event, and posts the audit as a message in your thread. I run mine weekly on Sunday evening. You could run it daily at 6am if your days move fast.

Here is the core prompt. Paste it into a new scheduled task and set when it runs:

Every Sunday at 6pm, read calendar-context.md, then look at my calendar for the coming week. Go through every event. Flag any conflicts or double-bookings, anything too tight to travel between, and anything that collides with my boundaries. Tell me whether this week is aligned with my priorities, and what to move if it isn't. Write it as a short brief I can read on my phone.

That alone is the audit. The rest of this article is how you make it yours.

4. Blocks you can paste in

The prompt above is the spine. Each block below is a paragraph you append to it. Add the ones you want, skip the ones you don't. This is exactly how mine is built.

Your week, audited Sunday 6:00 PM PRIORITIES 2 of 3 workouts scheduled. Thursday has no block, move the 4pm call. CONFLICTS Tue 2pm dentist overlaps Luna pickup. Wed is back-to-back 9 to 4, no lunch. WEATHER Rain Tue and Wed, 58 degrees. Bring the rain jacket Tuesday. MEALS Wed is slammed: slow cooker night. Fri: pasta, Luna approved. GROCERY LIST Produce: spinach, lemons, garlic Dairy: parmesan, butter Pantry: orzo, stock, chickpeas THINGS TO KNOW Thu school event needs a snack Sat party: RSVP still open Mon 10am: new client, see notes
What lands in my thread. Each block is one paragraph you add to the prompt, in any combination.

Priorities, at the top

Put this first, because it is the whole point. Everything else is detail.

Start the brief with a Priorities section. Compare this week against the priorities in calendar-context.md. Tell me plainly whether the week is aligned or not, what's missing, and the one change that would fix it.

Conflicts and crunch

Add a Conflicts section: double-bookings, two things too close together to travel between, days with no break, and anything that crosses a boundary in my context file. Suggest the specific move for each one.

Weather, and what to wear

It uses the location from your context file. This is the block that sounds silly and ends up being the one you read first.

Add a Weather section for my location for each day of the week. For any day with outdoor events or a commute, tell me what to wear and whether to bring a jacket or umbrella.

Meals, built around the week

Three ways to do this, pick one. It can suggest from your context file, where you listed your favorite meals and restaurants. It can pull ideas from the web. Or if you keep recipes somewhere it can connect to, it can draw from there. It also reads any meals you already put on the calendar.

Add a Meals section. Look at how busy each evening is and suggest a dinner for every night from the favorites in my context file: quick ones on packed days, something nicer on an open night. If I already have a meal on the calendar, keep it and plan around it. Suggest a restaurant for any night that's too full to cook.

If you want it pulling from the web instead, swap the middle sentence for: "Suggest five weeknight dinners from the web that fit my family's food rules in the context file."

Grocery list

Add a Grocery List section: every ingredient for the week's meals, grouped by aisle, with anything I likely already have marked as optional.

Things to know

Add a Things To Know section: anything in an event's notes that needs prep, RSVPs that are still open, anything that needs a gift, a snack, a form, or a drive.

Highlights and a little research

This one is optional and a real upgrade. It looks up the events themselves.

Add a Highlights section. For any meeting with a new person or company, do a quick bit of research and give me two lines of context. For any event at a venue, tell me parking and how long it takes to get there.

Put it all together

Mine, fully assembled, is the core prompt plus Priorities, Conflicts, Weather, Meals, Grocery List, and Things To Know. It runs Sunday at 6pm and the brief is sitting in my thread by the time the girls are down. Ten minutes reading it replaces an evening of replanning.

Remember: the agent is only as smart as the context file. If a brief feels generic, the fix is never a better prompt. It is a better answer to one of the interview questions.

What to notice

  • The file does the work. Your priorities, your people, your location, your food. Write it once, refresh it quarterly.
  • Priorities first, logistics second. A week with zero conflicts can still be the wrong week.
  • Blocks, not one giant prompt. Add them one at a time. Keep the ones you actually read.
  • Schedule it and walk away. The value is that you don't have to remember to run it.
I didn't get better at planning my week. I stopped being the one who had to.

If you haven't set up connectors or a context file yet, start with the full beginner setup. And if you want the same idea for your inbox, here is the email agent.