AI

I Automated My Weekly Planning With Claude Cowork. Here's How.

My week now plans itself (mostly)
Evan Tarver avatar
EVAN TARVER · MAY 26 2026 · 13 MIN READ

I’m a type-A planner. I’ve certainly spent a lot of time thinking about the best weekly planning frameworks that maximize my effectiveness (doing the right thing) and efficiency (doing that thing well).

I used to spend a couple hours every Sunday planning my week. If I even got around to it (though I hate to admit it).

When I did plan, I’d stare at my goals, manually break them into tasks, add those tasks to a project tracker, drag time blocks onto my calendar, and feel productive. Then Monday would happen. By Wednesday I’d forgotten half the plan. By Friday I had close to no idea what I actually accomplished versus what I intended to accomplish.

No post-mortem. No learning. Just starting from scratch the following week. Essentially running in place.

Then I set up one weekly planning automation in Claude Cowork. Now it kicks off every Friday at 4pm, runs a post-mortem on my week, references my annual and quarterly plans, and drafts next week’s schedule before I even open my calendar.

My planning went from 2 hours (inconsistently) to under 30 minutes (every week) while making me maximally effective and efficient.

Sound good? Because I’m going to walk you through exactly how to set this up.

Enjoying this? It started as an email.
One tactical email a week, before it hits the blog. Free, no fluff.

Why Planning Fails

I’m sure you’ve heard the saying, “failing to plan is planning to fail.”

And I’m sure you know that planning matters. So why don’t we do it well (if at all)?

Two reasons:

  1. The consistency problem. Planning takes too long when you do it manually, so you skip it. Then you skip it again. Then it’s been three weeks and you’ve been winging it, reacting to whatever feels urgent instead of working toward what actually matters.

  2. The post-mortem problem. Even when you plan, you never look back. You don’t compare what you planned to what you did. Which means you never learn that you consistently overestimate how many deep-work blocks you can fit into a day, or that your Tuesday meetings always blow up your afternoon focus time.

Each week starts from zero. No compounding. No improvement.

The fix isn’t more discipline. It’s removing yourself from the process.

The Framework: Annual Goals → Daily To-do’s

The planning system I built works like a funnel. Your annual goals feed into quarterly plans, which feed into weekly tasks and daily to-do’s, which get scheduled as actual calendar blocks.

Think of it this way:

  • Annual goal: Your North Star (ie, launch a paid community)

  • Quarterly plan: An outline of your priorities and strategies for the quarter

  • Weekly tasks: Breaking down your quarterly plan into weekly goals

  • Daily to-do’s: Translating your weekly goals into daily tasks

Most people have the annual goals written down somewhere. Maybe even quarterly plans. But the translation from quarterly → weekly → daily? That’s where it breaks down because it requires you to sit there, think through priorities, estimate time, and schedule blocks.

And then what about next week? And the week after that? Did you actually assess what you did and didn’t accomplish based on your plan? Did you carry those learnings forward for better planning? Doubtful.

Luckily, Claude Cowork can do all of that for you. And, it gets even better at it over time.

The Automation: Your Personal Planning System

All you need to do is set up one automation in Claude Cowork, and every week, it’ll do three things in sequence:

Step 1: Post-Mortem. Claude reviews my calendar and Notion tasks from the current week. What did I complete? What rolled over? What got added mid-week that wasn’t planned? It summarizes the wins and misses and asks me questions to ensure it’s right.

Step 2: Draft Next Week. Claude references my quarterly plan, looks at what’s due, considers what carried over from this week, checks my calendar for existing commitments, and drafts a full weekly schedule with specific time blocks for each task.

Step 3: Write to Calendar. Claude writes the draft directly onto my Google Calendar. By the time I sit down Friday evening, I have a complete proposed week waiting for me.

My planning automation runs every Friday at 4pm. I now spend less than 30 minutes each week reviewing it, making adjustments, and confirming. Compare that to the 2+ hours that used to eat into my Sundays doing it all from scratch (and the many weeks I spent doing nothing at all).

Decision Traces: How It Gets Smarter

This is the part that makes the system compound instead of staying flat.

Every week, Claude’s post-mortem creates decision traces. These are observations about my planning patterns that get stored and referenced in future weeks. Things like:

  • “Last three weeks, Tuesday afternoon deep-work blocks were interrupted by unscheduled calls. Consider blocking Tuesdays as meeting-free.”

  • “Content creation tasks consistently take 1.5x the estimated time. Adjusting future estimates.”

  • “Revenue tasks completed at 90% rate. Admin tasks completed at 40%. Deprioritizing or batching admin.”

Over time, these traces build a profile of how I actually work versus how I think I work (turns out there’s a big gap).

The result is that week 10 of planning looks nothing like week 1. Claude knows my patterns, my blind spots, and my realistic capacity. It stops scheduling three deep-work blocks on days I historically get pulled into fires. It pads time estimates for the task types I always underestimate.

Planning gets sharper every single week without me doing anything differently.

How to Set up Your Personal Planning Automation

Scheduled tasks are available on all paid Claude plans, the whole thing takes maybe 15 minutes to configure, and pretty much all you’ll have to do is chat with Claude Cowork to set it up.

What you’ll need upfront

  • The Claude desktop app installed

  • A Notion account (free tier is fine)

  • A Google Calendar (or whatever)

Step 1: Create the Cowork project

Create a dedicated project in Claude for weekly planning. This keeps your planning context separate from everything else you use Claude for.

  1. Open the Claude desktop app and switch to Cowork.

  2. Create a new project. Name it “Weekly Planning” or similar.

Cowork automatically creates a folder for the project on your computer (typically at Documents/Claude/Projects/[project name]). You don’t need to make one yourself. Claude will write a config file into it later — that’s how it remembers your setup across sessions.

Step 2: Connect Notion and Google Calendar

Notion acts as a database so Claude can read your annual goals, quarterly plans, and tasks. This is the “brain” of the system. Your goals live in Notion, and Claude pulls from them every week to generate relevant tasks.

Connect your calendar so Claude can both read your existing commitments (meetings, recurring events, blocked time) and write new task blocks directly onto your calendar. This is the part that makes planning feel automatic. You open your calendar Monday morning and your week is already structured.

In your new project, paste this:

“Help me connect Notion and Google Calendar to this project. Walk me through it.”

Claude will surface the connector cards and prompt you to click “Connect” on each. You’ll be redirected to Notion and Google to grant access. Approve everything Claude asks for.

When done, verify:

“Confirm both Notion and Google Calendar are connected. List my Notion pages and my available calendars.”

If it lists them correctly, you’re good.

Step 3: Let Claude build your Notion structure

This is where Claude does the heavy lifting. Paste this prompt:

“Set up my Notion workspace for weekly planning. I want this structure inside my main Teamspace:

  • Annual Goals page: top-level filter for the year

  • Quarterly Plans: parent page → sub-page for the current quarter

  • Weekly Plans: a database where each row is a week. Properties: Week Of (date), Goals (text), Day-by-day (text), Goals Achieved (text), Goals Missed (text), Mid-week Updates (text), Decision Traces (text)

  • Experiments & To-Do’s: a task database. Properties: Title (text), Status (select: Idea / Up Next / In Progress / Completed), Due Date (date), Notes (text), Project (relation to a Projects page)

  • A project hub page that organizes and links out to these pages

Walk me through each one, confirm with me before creating, then build them in Notion. When done, give me the URL or collection ID of each database — I’ll need these later.”

Claude will check in along the way. Approve each piece, edit anything you want to change.

Once it’s done, ask:

“Save those Notion database IDs and the structure overview to a file in my workspace folder. I’ll wire them into CLAUDE.md in the next step.”

Step 4: The personal-context interview

The system runs on a file called CLAUDE.md that Claude auto-loads every session. It’s the “brain” of the whole setup: your role, schedule, priorities, conventions, everything Claude needs to plan your week intelligently.

It’s essentially a set of instructions that teaches Claude how you work. Mine includes:

  • My working hours and energy patterns (deep work before noon, meetings after 2pm)

  • My time estimates for different task types

  • My priority hierarchy (revenue-generating work > content > admin)

  • Formatting preferences for calendar blocks

  • Rules like “never schedule more than 2 deep-work blocks per day”

The Claude MD file is what turns a generic AI assistant into your planning partner. Without it, Claude plans for a hypothetical person. With it, Claude plans for you.

Feel free to customize the prompt below for your own needs. For example, if you already have annual goals, you can just drop those into Notion. If not, you can have it ask you about your “strategic priorities” and will create goals for you.

Paste this:

“Interview me to build my CLAUDE.md. Ask me one section at a time, then draft that section before moving on. Cover:

  1. About me — what I do for work, what I’m building, where I live, key personal context (pets, family, anything non-negotiable about my daily life)

  2. Weekly schedule constraints — typical work hours, meals, exercise routine, any locked time blocks

  3. Standing rules — sacred time blocks (e.g., ‘Friday afternoon is buffer time’, ‘no meetings before 10am’, ‘dog walk every day at noon’)

  4. Strategic priorities — top 3-5 goals for this quarter and year

  5. Planning protocol — how I want you to plan with me (rule of thumb: list weekly goals → break into day-by-day → confirm in chat → only then push to calendar/Notion)

  6. Production workflows — how I make things (e.g., ‘video first, then transcript becomes article’)

  7. Calendar color conventions — colors I want for different event types

  8. Task structure conventions — granularity, naming, how I tag projects

  9. Notion source-of-truth structure — paste in the database IDs from Step 3

After each section, draft it, show me, and let me edit. When all sections are done, save the whole thing as CLAUDE.md in my workspace folder.”

Take this seriously. The more accurate this file is, the better every future planning session will go.

Step 5: Set up the Friday task

The auto-planning loop. Feel free to update the weekly time for your needs. Paste:

“Create a scheduled task that fires every Friday at 4pm in my local timezone. Name it friday-weekly-postmortem-and-plan. When it runs, it should execute this multi-step flow with explicit confirmation gates between each step:

Step 1: Post-mortem + task cleanup (combined). Read this week’s Weekly Plans entry, the current Experiments & To-Do’s tasks, the past week’s calendar events, and any Mid-week Updates. Draft (a) the post-mortem: goals achieved, goals missed, why slippage happened, decision traces; and (b) a cleanup list for every In Progress / Up Next task plus any lingering prior-week items — propose Completed, push to next week (update Due Date), or mark superseded/delete. Wait for my confirmation on both before continuing.

Step 2: Next-week goals draft. Use the post-mortem lessons, the Quarterly Plan, and the Content Calendar to draft 5-8 weekly goals in priority order. Wait for confirmation.

Step 3: Day-by-day breakdown. Apply all constraints from CLAUDE.md (schedule, standing rules, day themes) to turn the goals into a day-by-day schedule. Wait for confirmation.

Step 4: Push. Only after Step 3 is confirmed: close this week’s Weekly Plans entry, create next week’s, push calendar events, create new task entries, execute the task cleanup decisions from Step 1.”

Confirm Claude created the task by asking:

“List my scheduled tasks and confirm the Friday one is set up correctly.”

Step 6: Add minimal Cowork project instructions

The bulk of the config lives in CLAUDE.md, not in Cowork’s project instructions. The project instructions should just point at it. Ask Claude:

“Draft the Cowork project instructions for this project. Keep it minimal — just a pointer telling future Claude that the source of truth lives in CLAUDE.md in the mounted workspace folder, and that if the folder isn’t mounted, to ask me to mount it before doing any planning work.”

Then copy what Claude gives you into your Cowork project settings (Project → Settings → Instructions).

Why this split? You can update conventions any time by just editing CLAUDE.md, no copying back and forth into Cowork.

Step 7: Test the loop manually

Before relying on the Friday automation, run one cycle by hand:

“Walk me through the weekly planning flow right now as if it were Friday afternoon. Start with the post-mortem (I’ll fill in last week’s outcomes), then draft next week’s goals, then the day-by-day. Use all the gates.”

Step through it. Check that:

  • Claude reads from Notion correctly

  • The day-by-day respects your schedule constraints

  • The calendar push works (events appear in Google Calendar with the right colors)

  • The task creation in Notion works

If anything feels off, fix it in CLAUDE.md and try again.

Step 8: Iterate as conventions emerge

The system improves the more you use it. When you notice a new pattern — a calendar color you want, a workflow tweak, a recurring time block — just tell Claude:

“Update CLAUDE.md with this: [the new convention].”

It edits the file directly. Future sessions pick it up automatically.

Enjoying this? It started as an email.
One tactical email a week, before it hits the blog. Free, no fluff.

Try It This Week

The whole system takes about 15 minutes to set up and one Friday cycle to see the value.

If you’ve been winging your weeks, or spending hours on planning that doesn’t stick, or starting every Monday from scratch, this fixes it. Not with more willpower. With one automation that runs whether you feel like planning or not.

Set up the Claude Cowork project this week and let me know how your first automated planning session goes.

What does your current weekly planning process look like? (Be honest.) Reply and tell me :)

For more automations with Claude Cowork, check out my article on creating an AI CRM that manages your outreach and sales pipeline.

Evan Tarver avatar
Evan Tarver

Writer, founder, and AI builder. Currently building Flyletter, previously sold Selling Signals (100k+ subscribers). 1 sold, 2 failed, 1 active. This post started as an issue of my weekly newsletter.