Proactive Chief of Staff
Use this pattern when you want a personal operations layer that prepares meeting context, flags calendar conflicts, and delivers useful reminders in one channel. It needs access to your calendar and work systems. Start read-only, then add any write-capable integration deliberately.
How it works
Section titled “How it works”- A heartbeat schedule checks the calendar on an interval you choose.
- Before meetings, the persona gathers attendee context, related Jira tickets, Confluence pages, and past notes from the integrations you configure.
- It prepares a brief with talking points and open items, then sends it to your preferred channel.
- It can surface calendar conflicts, overdue tasks, and approaching deadlines.
What you need to configure
Section titled “What you need to configure”- Scheduling, including a heartbeat interval that fits the calendar API and your tolerance for notifications
- A Google Calendar MCP or another calendar integration
- An Atlassian MCP for Jira and Confluence if those systems should contribute context
- A memory system for past notes and decisions
- A delivery channel such as Slack, Telegram, or terminal
Boundaries to set before it runs
Section titled “Boundaries to set before it runs”- Give the persona read-only calendar and work-system access first. Do not give it task, calendar, or message write access because a workflow page sounds convenient.
- Decide which meetings merit a brief and where proactive messages may appear. A briefing bot that pings every thirty minutes becomes wallpaper.
- Treat generated summaries as working context. Review them before relying on them for a decision or sending them onward.