How I built a morning brief that’s designed for exactly one person: me

18 min. read

Learning Center

Every weekday at 07:30, Claude reads my calendar, inbox, Slack and meeting notes, rewrites my to-do list and emails me the one thing that matters.

Every weekday at 07:30, before I've finished my first coffee, Claude has already read my calendar, my inbox, my Slack, my meeting notes, my project tool and my CRM. It has rewritten my to-do list, picked two candidates for the one thing that matters most today, and emailed a short version to my phone.

To get there, I sat down with Claude and let it interview me.

That's the part I want you to steal. Productivity apps are built for an average person who doesn't exist. I wanted something built around how my brain actually works. For me that means ADHD tendencies: long lists make me freeze, too many options make me stall, and starting is much harder than continuing. So my system never shows me more than 3 things for today, and never asks me to choose between more than 2.

Your version will look different. Maybe you're a night owl, maybe you're drowning in meetings, maybe you just hate email. The method is the same: get Claude to understand you first, then build the system together.

This guide walks through the whole thing, end to end. It's long. Grab a coffee.

What you'll end up with

A scheduled task that runs every weekday morning and does 7 things, in order:

Reads your to-do list first. One plain text file on your computer is the single source of truth.
Pulls fresh context from your calendar, email, chat, meeting notes and (optionally) your project tool and CRM.
Triages everything into a fixed vocabulary: Today, Rest of today, Later, Scheduled, Delegate or Kill.
Picks 2 candidates for the one thing, and says plainly which one has the deadline and which one has the money.
Rewrites your to-do file in place. It's a full rewrite every time, so nothing piles up.
Writes a full desktop brief as a file you read on your laptop.
Emails a short phone digest to you (and only you).

The whole run takes a few minutes. I read the phone version on the ferry from NDSM to Pontsteiger on my way to the office, and the desktop version when I sit down.

What you need

The Claude desktop app, with Cowork and scheduled tasks. Cowork is the mode where Claude can work with files on your computer and use your connected apps. Scheduled tasks let you save a prompt and have it run automatically on a timetable. Check that both are available on your plan before you start.

A folder on your computer. This is where your to-do file, your daily briefs and your personal rules live. I call mine "Daily Operating System".

A way to read markdown files. Markdown is just plain text with light formatting (a # for a heading, - [ ] for a checkbox). Any text editor opens it. I use Obsidian (the free version), because it renders the files nicely and I can point it straight at the folder. Any markdown viewer works.

Your tools, connected to Claude. Here's what I connect, by category. You don't need all of them. Start with the first 3.

Category	What it gives the brief	What I use	Works just as well
Calendar	Today's meetings, clashes, prep	Google Calendar	Outlook, iCloud
Email	Unread mail, and what you've already sent	Gmail	Outlook
Team chat	DMs and mentions since yesterday	Slack	Teams, Discord
Meeting notes	Action items from recent meetings	Granola	Fireflies, Otter, Zoom notes, Fathom
Project tool	Tasks assigned to you	Productive	Asana, Linear, Monday, Jira, ClickUp
CRM	Relationships going cold, deals slipping	HubSpot	Salesforce, Pipedrive, Close
Shared docs	Running notes you keep with partners	Google Docs	Notion, Word online
Messages	Texts since yesterday	iMessage	WhatsApp (if a connector exists)

Why I pull all of these: my work is scattered. A client promise can live in a meeting transcript, the follow-up in email, the internal nudge in Slack and the deadline in the calendar. Pulling from all of them is how the brief catches promises I forgot I made.

Step 1: Let Claude interview you

Skip this step and you'll build a generic system you'll abandon within 2 weeks. I know because I've done it.

Open a normal Cowork chat, point it at your new folder, and paste this:

I want to build a personal morning brief that runs every weekday as a
scheduled task. Before we build anything, I want you to understand how I
work. Interview me. Ask one question at a time and wait for my answer.
Keep going until you understand me well enough to design the system.

Cover:
- My role, what a good day looks like, and what a bad day looks like
- My energy through the day: when I do my best thinking, when I crash
- How I react to long to-do lists, too many options, interruptions
- What I tend to forget, avoid, or leave until too late
- Which days are different (days off, travel days, meeting-heavy days)
- The tools I use for calendar, email, chat, meetings, projects, clients
- Where I want to read the brief (laptop, phone, both) and when
- The people and clients who matter most, and how I refer to them
- Words I use for my own planning (e.g. "today", "later", "park it")
- Anything I've tried before that didn't stick, and why

When you're done, write a file called about-me.md in this folder that
captures everything as rules the morning brief should follow. Keep it
short and specific. Then show it to me so I can correct it.

Answer honestly. The more specific you are, the better it gets. "I get overwhelmed" is less useful than "if I see more than 3 things for today I don't start any of them".

Here's roughly what came out of my interview:

Predominantly inattentive ADHD tendencies. Long lists cause freeze, decision fatigue is real, and switching context is expensive.
My day has 5 blocks: setup, deep work, comms, collab and shutdown. The brief maps everything onto them.
Hard cap of 3 items in Today.
Exactly 2 candidates for the one thing, never more.
Wednesday is my day off. No external meetings, and a much lighter brief.
My planning words are Today, Later, Schedule, and Delegate or Kill. The brief uses those and nothing else.

Personal rules file template. If you'd rather start from a skeleton, here's the structure mine settled into:

# About me — rules for my morning brief

## Who I am
- Role: [YOUR ROLE] at [YOUR COMPANY]. Based in [CITY], timezone [TZ].
- What only I can do: [e.g. win new work, set direction]

## How my brain works
- [e.g. Long lists make me freeze. Max 3 items in Today.]
- [e.g. Too many options stall me. Give me exactly 2 to choose from.]
- [e.g. Starting is harder than continuing. Make the first step tiny.]
- [e.g. I forget promises I make in meetings. Hunt for them.]

## My day
- Blocks: [e.g. setup 08:00–09:15 · deep 09:30–12:00 · comms · collab · shutdown]
- Best thinking: [e.g. mornings]. Worst: [e.g. after 15:00]
- Days off / light days: [e.g. Wednesday = off. Only flag real fires.]

## My vocabulary
- Today (max 3) · Rest of today · Later · Schedule · Delegate / Kill

## People
- [Name] = [role]. [Name] = [role]. (Short list, the ones who show up daily.)

## Where I read it
- Desktop: full brief as a file in [FOLDER]
- Phone: short digest emailed to [YOUR OWN EMAIL] only

## Things to ignore
- [e.g. award entries, newsletters, internal all-hands chatter]

Correct it until it reads like you. This file is the foundation for everything else.

Step 2: Set up your folder

Here's the structure I use. Create it inside your chosen folder:

Daily Operating System/
├── about-me.md                     ← your rules (from Step 1)
├── TASKS.md                        ← your to-do list, the single source of truth
├── morning-brief-prompt.md         ← a copy of your scheduled-task prompt
├── archive/
│   └── tasks-archive.md            ← finished and stale items, append-only
└── 2026-09-29-morning-debrief.md   ← one brief per day, created automatically

Why one TASKS.md file: before this, my tasks lived in 5 places and none of them was the truth. Now there's a hard rule: if TASKS.md and anything else disagree, TASKS.md wins. The daily briefs are snapshots. The archive is the memory.

Why keep a copy of the prompt: you'll tweak it a lot in the first few weeks. A copy in the folder makes it easy to see what changed and roll back.

Step 3: Connect your tools

Connect them one at a time, and test each one before moving on.

In the Claude desktop app, open the connectors settings and add your calendar, then your email, then your chat tool.
For each one, sign in and approve access. Read what you're approving.
Back in a Cowork chat, test it in plain language: "What's on my calendar tomorrow?" "Show me my unread email from the last 2 days." "Any Slack DMs to me since yesterday?"
When all 3 work, add the optional ones: meeting notes, project tool, CRM, shared docs, messages.

A few things I learned the hard way:

Check each tool actually returns data. A connector can look "connected" and still be missing a permission. If a test returns nothing or an error, reconnect it and look for the extra permission it needs.
Some local apps need system permissions. Reading Messages on a Mac, for example, needs a privacy permission in your system settings. If it fails, the brief should say so and carry on without it.
Your CRM will be noisier than you think. Mine was full of spam bookings and internal test contacts. More on filtering that in Step 5.

Step 4: Create your TASKS.md

Ask Claude to create it from this template, or paste it in yourself. Keep the section order. The morning run rewrites the file in this exact order every day.

# 👑 Tasks
Last triaged: YYYY-MM-DD · TASKS.md is the single source of truth

---

## ⭐ [Weekday DD Mon] — pick THE ONE
**A — [candidate].** [Why it matters, what the deadline is.] · src: [source]
**B — [candidate].** [Why it matters, what the deadline is.] · src: [source]
*[One line: which one has the clock, which one has the money.]*

---

## 📌 Today (max 3)
- [ ] [Item] · src: [source]
- [ ] [Item] · src: [source]
- [ ] [Item] · src: [source]

---

## ⏱ Time blocks
- setup [time] — [what]
- deep [time] — [what]
- comms [time] — [what]
- collab [time] — [what]
- shutdown [time] — [what]

---

## 🆕 NEW
*Your capture lane. Drop anything here during the day. Tomorrow's run sorts it.*

---

## 📋 Rest of today
- [ ] [Quick win] · src: [source]

---

## 📅 Later
### Client / external
- [ ] [Item] `carried 0d` · src: [source]
### Internal / ops
- [ ] [Item] `carried 0d` · src: [source]
### Personal / admin
- [ ] [Item] `carried 0d` · src: [source]

---

## 🗓 Scheduled
### This week
- [Day]: [event or deadline]
### Later
- [Date]: [event or deadline]

---

## 🤝 Delegate / Monitor / Kill
- [Item] → [owner]. · src: [source]
- ❌ Killed: [item] — [reason]

---

## 🚫 Blocked
- [ ] [Item] — waiting on [who/what]

---

## 🔗 Project tool sync
[Live count + the few items that matter. Rewritten every run.]

---

## 📇 CRM sync
[Live count after filtering + relationships going cold. Rewritten every run.]

---

## 📊 Carry pressure
[Anything moved 3+ days. What you owe people vs what you're chasing.]

---

## 🆕 Changes since last triage
- ✅ Done: …
- ➕ Added: …
- 🗑 Archived: …

---

## ⚖️ Reminders
- Max 3 in Today.
- Client work beats internal work.
- Verify against the source, not the board.

Format rules that make this work:

One short sentence per item. Paragraphs hide the action.
Every item ends with its source (src: Gmail, src: Slack, src: meeting notes Sep 25). Meeting-note tools sometimes turn banter into action items. The source tag lets you check in 5 seconds whether something is real.
Carry counters. Every run bumps carried Nd on untouched items. At 3 days it gets a ⚠️ and a "break down or kill" flag. At 14 days it's archived automatically. You'd be amazed how much stops haunting you once it's allowed to die.
Tick things off during the day. Change - [ ] to - [x], and add a word if it helps: done, killed, delegated to Sam. Tomorrow's run reads your ticks first.

Step 5: Write the scheduled-task prompt

This is the engine. Below is a cleaned-up version of mine with placeholders. Paste it into a Cowork chat first (Step 6) before you schedule it.

Run [YOUR NAME]'s morning brief. This is the daily kickoff.

CANONICAL FILE: TASKS.md in the [FOLDER NAME] folder is the single source
of truth. Read about-me.md for personal rules before anything else.

BEFORE YOU START
- Check today's day of the week. If it is [DAY OFF], skip the full flow.
  Only scan [chat tool] DMs and messages since yesterday, and only surface
  something if it's truly on fire (client escalation, deadline today,
  team blocked). Otherwise reply "It's [DAY OFF]. Nothing to brief." No email.

STEP 1 — GATHER (in parallel)
- TASKS.md: read it FIRST. Hold its state as the baseline.
- Calendar: today + tomorrow.
- Email: unread in the inbox from the last 2 days, AND everything I sent
  in the last 7 days (to see what I've already answered).
- Chat: my DMs and @mentions since yesterday.
- Meeting notes: open action items from the LAST 5 BUSINESS DAYS, not
  just yesterday.
- [Optional] Project tool: my open tasks, pulled live every run. Ignore
  [e.g. HR checklist projects]; only [e.g. client/partner projects] matter.
- [Optional] CRM: records I own. Apply the noise filter below first.
- [Optional] Shared docs: my open items from the last 2 weeks only.
- [Optional] Messages: unread from the last 24h. If access fails, say so
  in the brief and carry on.

CRM NOISE FILTER (apply before triage)
- Suppress: blank or "N/A" company with a personal email domain, internal
  colleagues, test records, auto-generated system contacts.
- Always keep: anyone who matches a name already in TASKS.md.
- Report the suppressed count so I can sanity-check the filter.
- A contact is "going cold" only if their last logged touch is 90+ days
  old AND they connect to something live in TASKS.md. Everyone else is one
  count line, not a to-do list.
- If many records share the exact same last-contacted timestamp to the
  second, it's a bulk import. Say so and don't count it as real activity.

STEP 2 — TRIAGE (against the TASKS.md baseline)
Sort every open item into: Today (HARD CAP 3) · Rest of today (quick
wins) · Later (Client / Internal / Personal) · Scheduled (date-bound) ·
Delegate/Monitor (with owner) or Kill (with reason).
- Read my ticks and inline notes first (done / killed / delegated).
- Archive ticked items to archive/tasks-archive.md (append-only).
- Bump "carried Nd" on untouched items. 3+ days = flag. 14+ days =
  auto-archive unless date-bound.
- New items that land after noon go on tomorrow's list, not today's.
- Cross-reference: if a task shows up in today's meetings, email or chat,
  add that context.

VERIFY BEFORE YOU ACCUSE (hard rule)
Before telling me I owe someone a reply or haven't sent something, check
my sent mail and chat for that specific item. Assume the list is ~12
hours behind what I've actually done.

STEP 3 — PICK THE ONE THING
Exactly 2 candidates. Both must be high impact AND only-I-can-do-it.
Prefer unfinished prep for a meeting today or tomorrow over open-ended
work. Say plainly which one has the clock and which one has the money.

STEP 4 — REWRITE TASKS.md IN PLACE
Full rewrite, same section order. Update "Last triaged". Every item gets a
src tag. Self-check: max 3 in Today, exactly 2 candidates, counters
bumped, stale items archived.

STEP 5 — WRITE THE DESKTOP BRIEF
Save as YYYY-MM-DD-morning-debrief.md in the folder. Sections:
- #1 priority today (A or B)
- Today's schedule: table with Time | Meeting | Prep | Block. Flag clashes.
- What's new since yesterday (changes only)
- Meeting prep: 1–2 bullets per meeting
- Email: active + needs reply (table)
- Chat follow-ups (numbered, specific)
- [Optional] CRM follow-ups (only what survives the filter)
- Top 3 moves today: concrete, time-estimated, mapped to my blocks
- Next few days preview (flag anything booked on my day off)
- What changed in the to-do list

STEP 6 — EMAIL THE PHONE DIGEST
SEND an HTML email to [YOUR OWN EMAIL ADDRESS] and nobody else. Never add
another recipient, cc or bcc.
- Subject: "👑 [Day DD Mon] — [the single sharpest thing about today]".
  The subject must carry real information; often it's all I'll read.
- Include ONLY: the 2 candidates, today's schedule (time + one line),
  top 3 moves, what changed (max 5 bullets). Everything else stays on
  the desktop.
- End with: "Full brief: YYYY-MM-DD-morning-debrief.md"
- Send both an HTML body and a plain-text body with the same content.
- Follow the email template rules in about-me.md (or below).

STEP 7 — CONFIRM
Link the brief file, confirm TASKS.md was rewritten and the email sent,
and ask: "Pick A or B — or want me to re-order?"

ALWAYS
- Max 3 in Today. Never more than 2 options when I have to choose.
- Client work beats internal work.
- Never book or accept anything on my day off. Flag it if it appears.
- Tag every task with its source.
- [Anything else from about-me.md you want enforced every single day.]

Why each rule is there. Every line in that prompt exists because something went wrong without it:

Read TASKS.md first. Otherwise Claude builds a fresh list from the inbox and forgets everything you parked last week.
Sent mail, not just unread. Early on the brief kept telling me I owed people replies I'd already sent. Checking outbound mail fixed most of it.
5 business days of meeting notes. One day of lookback missed everything promised on a Tuesday and due on a Friday.
Verify before you accuse. Some mornings 3 "you still owe this" items had already been done, a few of them on my day off. A brief that nags you about finished work stops being trusted.
2 candidates, clock vs money. My hardest decisions are usually between the urgent thing and the thing that pays. Naming which is which makes the choice take seconds.
After noon goes to tomorrow. Otherwise the afternoon keeps growing Today past 3.
Only email yourself. The brief sends mail automatically. Lock the recipient to your own address and never let it add anyone.

Step 6: Test it by hand before you schedule it

Paste the prompt into a Cowork chat with your folder selected and let it run. Then check:

Is TASKS.md in the right order, with max 3 in Today and exactly 2 candidates?
Are the sources real? Open 3 random items and check the src tag against the actual email, message or meeting note.
Did it claim you owe something you've already done? If so, tighten the "verify before you accuse" rule.
Is the schedule right? Timezones catch everyone at least once. Say your timezone explicitly in about-me.md.
Did the email arrive, and does it read well on your phone?

Fix, re-run, repeat. It took me about a week of daily corrections before I stopped editing it every morning.

Step 7: Schedule it

Once a manual run looks right:

Open scheduled tasks in the Claude desktop app and create a new task.
Give it a name ("Morning brief"), paste in your prompt, and make sure your folder is attached.
Set it to run on weekdays at a time before you usually start. I use 07:30.
Save it, then check the first automatic run the next morning.

Two things to know:

Scheduled runs happen without you. Claude can't stop and ask you questions, so the prompt has to be explicit about what it may do on its own. Mine may rewrite TASKS.md, write the brief, and send one email to my own address. Nothing else. If it isn't sure, it should report, not act.
Your computer may need to be on and the app open for the task to run on time. Check the scheduled-tasks settings for how yours behaves.

Step 8: Make the phone version actually readable

I read the brief in two places. On the laptop, the full version with tables. On the phone, a digest built for deciding and moving. Put the full brief on a phone and you get exactly the freeze this system exists to prevent.

Email apps aren't browsers, so the digest has strict layout rules. Put these in about-me.md so every run follows them:

Inline every style. Email apps strip style blocks.
Use tables for layout, single column, max width 620px.
Body text at least 16px. Anything smaller and your phone zooms in and wrecks the layout.
Set a background and text colour on every block, so dark mode can't turn it into mush.
The schedule has 2 columns only: a narrow time column and a content column. Anything wider is unreadable on a phone.
Clashes get a small coloured pill, not a row of warning emojis.
Keep the look identical every day. You should recognise it at a glance.

Email digest template. Give this to Claude as the skeleton. Swap the colours for your own brand.

<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" style="background:#f4f2ee">
<tr><td align="center" style="padding:20px 12px;background:#f4f2ee">
<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" style="max-width:620px;background:#ffffff;border-radius:14px">

  <!-- Header -->
  <tr><td style="background:#ffffff;color:#1a1a1a;padding:26px 22px 8px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,sans-serif">
    <div style="font-size:13px;letter-spacing:2px;text-transform:uppercase;color:#b8860b;font-weight:700">Morning Brief · [Weekday DD Month]</div>
    <div style="font-size:22px;line-height:1.35;font-weight:700;color:#1a1a1a;padding-top:8px">[One sentence: the sharpest thing about today.]</div>
  </td></tr>

  <!-- Pick A or B -->
  <tr><td style="background:#ffffff;color:#1a1a1a;padding:18px 22px 4px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,sans-serif">
    <div style="font-size:13px;letter-spacing:2px;text-transform:uppercase;color:#b8860b;font-weight:700;padding-bottom:10px">⭐ Pick A or B</div>
    <div style="font-size:16px;line-height:1.5;color:#1a1a1a;padding-bottom:12px"><b>A — [candidate].</b> [Why. When.] <i>[Clock or money.]</i></div>
    <div style="font-size:16px;line-height:1.5;color:#1a1a1a;padding-bottom:12px"><b>B — [candidate].</b> [Why. When.] <i>[Clock or money.]</i></div>
  </td></tr>

  <!-- Today: 2 columns only -->
  <tr><td style="background:#ffffff;color:#1a1a1a;padding:20px 22px 4px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,sans-serif">
    <div style="font-size:13px;letter-spacing:2px;text-transform:uppercase;color:#b8860b;font-weight:700;padding-bottom:6px">🗓 Today</div>
    <table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" style="background:#ffffff">
      <tr>
        <td style="white-space:nowrap;vertical-align:top;padding:8px 12px 8px 0;font-size:16px;font-weight:700;color:#1a1a1a;border-top:1px solid #eeeae3">[09:30]</td>
        <td style="vertical-align:top;padding:8px 0;font-size:16px;line-height:1.45;color:#1a1a1a;border-top:1px solid #eeeae3"><b>[Meeting]</b> <span style="display:inline-block;background:#f6e7df;color:#a4502a;font-size:12px;font-weight:700;padding:2px 8px;border-radius:10px">[clash]</span><br><span style="color:#555555">[One-line prep.]</span></td>
      </tr>
      <!-- repeat rows -->
    </table>
  </td></tr>

  <!-- Top 3 moves -->
  <tr><td style="background:#ffffff;color:#1a1a1a;padding:20px 22px 4px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,sans-serif">
    <div style="font-size:13px;letter-spacing:2px;text-transform:uppercase;color:#b8860b;font-weight:700;padding-bottom:8px">🎯 Top 3 moves</div>
    <div style="font-size:16px;line-height:1.5;color:#1a1a1a;padding-bottom:8px"><b>1.</b> [Move] <span style="color:#555555">[time · block]</span></div>
    <div style="font-size:16px;line-height:1.5;color:#1a1a1a;padding-bottom:8px"><b>2.</b> [Move] <span style="color:#555555">[time · block]</span></div>
    <div style="font-size:16px;line-height:1.5;color:#1a1a1a"><b>3.</b> [Move] <span style="color:#555555">[time · block]</span></div>
  </td></tr>

  <!-- What changed -->
  <tr><td style="background:#ffffff;color:#1a1a1a;padding:20px 22px 22px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,sans-serif">
    <div style="font-size:13px;letter-spacing:2px;text-transform:uppercase;color:#b8860b;font-weight:700;padding-bottom:8px">🚨 What changed</div>
    <div style="font-size:16px;line-height:1.5;color:#1a1a1a;padding-bottom:6px">• [Change, max 5 bullets]</div>
  </td></tr>

  <!-- Footer -->
  <tr><td style="background:#1a1a1a;color:#f4f2ee;padding:16px 22px;border-radius:0 0 14px 14px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,sans-serif;font-size:15px">Full brief: <b>[YYYY-MM-DD]-morning-debrief.md</b></td></tr>

</table>
</td></tr></table>

Step 9: Keep teaching it

The first version will be about 70% right. The magic happens in the weeks after, when you correct it and it remembers.

Whenever the brief gets something wrong, tell Claude in a chat, and ask it to add the fix to about-me.md or to the prompt. Some of my real corrections:

"Tag every task with where it came from. The meeting-notes tool sometimes turns banter into action items."
"Before you flag a client deliverable as mine and overdue, check whether the person I delegated it to already shipped it."
"Prep for tomorrow's meeting beats open-ended proposal work for the one thing."
"Two invites at the same time from different people might both be real. Flag the overlap. Don't tell me to decline one."
"Award entries aren't productive for me. Stop surfacing them."
"The CRM's last-contacted date only shows what was logged there. It isn't proof a relationship went cold."

Every one of those came from a morning where the brief annoyed me. Annoyance is data. Feed it back.

Retire what you stop using. I used to mirror my list into a notes app. Once I stopped opening it, I told Claude to stop writing to it, and the system got simpler. Do the same with sources that go stale. A running doc that hasn't been edited in 4 months is costing you tokens and attention.

Guardrails I'd set from day one

The brief only ever emails you. Write your own address into the prompt and forbid any other recipient.
It drafts, you send. Anything that goes to another human (replies, Slack messages, invites) should be a draft you approve.
Read-only by default for everything else. It may rewrite your own files. It shouldn't change your CRM, your calendar or your project tool unless you ask in a live chat.
Watch what your tools log. I BCC my CRM on work email, and one day a personal thread got logged with it. Check occasionally, and keep personal mail out.
Protect your days off. Mine runs in a light mode on Wednesdays and flags anything that sneaks onto that day.

If something goes wrong

The brief is missing a source. Test that connector on its own in a chat. Usually it needs reconnecting or an extra permission.
It keeps nagging you about finished work. Tick things off in TASKS.md during the day, and make sure the prompt checks your sent mail.
Today has more than 3 items. Then the list is wrong. Tell it to push the rest to Later.
It's too long to read. Cut sections from the desktop brief. You'll know within a week which ones you skip.
The task didn't run. Check your computer was awake and the app was open at the scheduled time.

The point of all this

For me the magic is that the system fits me: my blocks, my words, my blind spots, my day off. It took one honest interview and a few weeks of corrections.

Yours will look nothing like mine, and it shouldn't.

If you want help building something like this for your team, that's the kind of thing we do at Your Majesty. Say hi at yourmajesty.co.

And if you want more of this in your inbox, I write a newsletter called 10 Things. Sign up here.

More soon, G