Editorial calendars

The week's slots, owners, and angles, on one doc.

Writers and the founder poke at the calendar. Agent connect swaps two slots without a new paste.

Set it up for your agentHow agent connect works
liveeditorial/october.md

October editorial calendar

Owner: Sonia Alvarez. Product: Glimmerpost. Three posts a week.

October calendar for Glimmerpost. Three posts a week, with an owner and an angle on each. Posts still go to the CMS one at a time. This file is the plan, not the publish button.

Not ready

The folder-to-send tutorial uses examples/send. That repo is still being filled in.

Bea will not ship that angle until the example repo builds from a clean checkout. Keep the tutorial on the calendar. Do not put it on a day when the repo is empty.

This week

Monday: folder-to-send tutorial. Thursday: pricing post.Monday: pricing post. Thursday: tutorial.

Owners

  • Monday: Bea, folder-to-send tutorial.Monday: Sonia, pricing FAQ angle.
  • Thursday: Sonia, pricing FAQ.Thursday: Bea, folder-to-send tutorial.
  • Wednesday stays the office-hours post. Arjun owns it, and it does not move.

Rules

  • One angle per post. If the repo is not ready, the angle moves, not the promise.
  • Pricing FAQ uses the docs wording. No feature we do not ship.

Next week

  • Tuesday: a short note on sending from a folder, only if examples/send builds from a clean checkout.
  • Friday: office hours recap. Arjun drafts it from the questions, not from a slogan.

examples/send

Bea Lindgren

The tutorial example repo is not ready. I would not ship that angle this week.

Arjun Patel

Keep the tutorial. Not this week.

Monday: folder-to-send tutorial

Arjun Patel

@agent move the pricing post to Monday and push the tutorial to Thursday.

agent

Moved pricing to Monday and the tutorial to Thursday.

resolved
Start with @agent to ask the agent
ResolveReply
Fictional example: a Glimmerpost October calendar in Gander, with a writer thread and a scripted agent connect reply.

How editorial calendars get reviewed today

A spreadsheet is a solid calendar. Comments on a cell do not reach the agent that drafted the angles in a markdown file.

A chat thread can swap Thursday and Monday in one message, and then the file is wrong until someone edits it. A meeting works when everyone is free, which is the problem a calendar is trying to avoid.

Swap Monday and Thursday

Sonia Alvarez asks her agent for Glimmerpost's October calendar: three posts a week, with owners and angles. She runs gander watch on editorial/october.md and sends the link to Bea Lindgren and Arjun Patel.

Bea highlights the tutorial angle and says the example repo is not ready. Arjun replies to keep the tutorial, but not this week. Human thread.

Arjun starts a new comment: "@agent move the pricing post to Monday and push the tutorial to Thursday." Sonia's agent swaps the slots, replies, and resolves the thread. Bea sees the new week on the same link. The calendar stays the planning doc. Posts still go to the CMS one at a time.

Who's in the doc

WriterWriter on the teamFounderThe author's agent

Writer Head of content. Sends the week's doc.

Writer on the team Checks that their slot is real.

Founder Checks the order against what the company is saying that week.

The author's agent Moves slots when someone uses agent connect.

Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.

Agents that fit editorial calendars

Grok BotA calendar drafted from a brief, with agent connect through MCP.
Claude CodeWhen the calendar lives in the repo, the session hears agent connect through MCP.

Swap the slots on the live calendar. Do not keep the real order in a chat message.

See how it works on the homepage