Claude

Two Skills, One Notion: The Operations Hub Behind My Morning

I’ve written about two skills in the last couple of weeks. The morning briefing one that reads Gmail, Outlook, Teams and my calendar so I don’t have to. The pre-call brief one that writes a context page for every meeting on my calendar before I sit down. Both posts mentioned Notion, mostly in passing, as the place the calendar lives. A friend asked me last week what that actually looked like. He’d built the pre-call skill from the post, pointed it at a single-table Notion database, and watched it produce briefs that were missing half the context he expected. The skill wasn’t the problem. The Notion underneath it was.

Thursday, May 28, 2026 | 16 minutes Read

The Briefing Skill That Builds Itself Around You

I ended the pre-call brief post with a section called “the setup”: a four-step recipe for building the same thing yourself. A call-prep skill, a scheduled task, a Notion database, a way to get the brief in front of you at join time. Here’s the shape, off you go. That’s the bit people wrote to me about. And the honest answer is that the recipe isn’t enough, because every post I’ve written about this (that one, and the morning briefing one before it) describes my setup. My Gmail. My Outlook for Mac. My Teams. A Notion database fed by a Mac app I built. “Here’s the shape, go build it” really means “copy my skill and rewrite half of it for your stack.” Which is a rubbish answer to give someone.

Thursday, May 28, 2026 | 3 minutes Read

Two Files, One Habit: How Agentic Coding Projects Are Learning to Remember

This started over a cup of coffee. My friend has been working on the people side of agentic coding. How do you actually get a team of engineers good at these tools on a large codebase, instead of two enthusiasts loving them and everyone else quietly going back to their old habits? Training, enablement, the unsexy stuff that decides whether a tool sticks. That was the conversation. What works, what falls apart at scale, the patterns people are landing on for serious projects. At some point I mentioned what I do with state and worklog files, and the thing snowballed. He hadn’t seen the pattern before. I’d been doing it for so long I’d stopped noticing it was a pattern. So I went home and started writing it down.

Tuesday, May 26, 2026 | 11 minutes Read

The Pre-Call Brief That Writes Itself

I take a lot of calls. Partner syncs, customer technical reviews, internal architecture chats, the occasional demo. On a bad week it’s eight a day. On a good week it’s also eight a day, just with more interesting topics. Eight calls a day is more than my brain wants to hold. I would join a customer call having genuinely forgotten what we discussed three weeks ago. I would walk into a partner sync and spend the first ten minutes catching up to context I should have had on the way in. Sometimes I’d realise mid-call that I’d committed to send something last time and never had.

Tuesday, May 26, 2026 | 7 minutes Read

The Morning Briefing I Don't Have to Write

Every morning starts the same way. Coffee, desk, the slow dread of opening four different surfaces to figure out what I missed. Gmail for personal. Outlook for work. Teams for whatever the team was arguing about in the Workflows chat at 11pm. And the calendar, because none of that matters if I’m walking into a meeting I forgot about in twenty minutes. Doing that reading manually takes about twenty minutes. Most of it is junk. The handful of things that actually matter are buried somewhere between a “FYI” message and an Apple developer notification I should have read three days ago.

Tuesday, May 26, 2026 | 6 minutes Read