You've learned to use AI. Now have it work for you.

A skill is how your agent does the same job, the same way, every time. You'll learn what makes a real skill, how to write one that actually works, and how to build a small library you can reuse across every agent. By the end of the day, your Chief of Staff has its first two skills running on demand.

Memory is the difference between an agent that gets sharper every week and one you re-brief every Monday. You'll learn what your agent should remember, what it should forget, and where memory sits in the platforms you're using. You'll set up working memory (today's context) and long-term memory (what compounds over time).

You already use connectors with your assistants for calendar, email, Slack, and Drive. Agents use the same ones. You'll learn what changes when an agent uses them on its own, why you start read-only, and which to set up for your Chief of Staff first.

The Chief of Staff goes end to end. It reads your calendar and email, decides what matters, and takes action: blocks prep time, adds tasks to your list, archives the noise. You'll see where it gets it right, where it doesn't, and how to tighten the gaps.

Sales: Pipeline Hygiene agent. Finance: Month-End Close agent. Operations: Project Triage agent. Product: Feedback Triage agent. We'll help you find the patterns in your role you could automate and pick your next agent. Then write the job description.

This is where the OS pays off. You don't start from scratch. The agent inherits your identity, your context, your memory. You add what's specific: its job, its skills, its boundaries. You'll learn what to share across agents and what each agent needs on its own.

By Wednesday you have an Agent OS running two agents. Today you write the Playbook. The act of writing it is the work: it forces you to name what you built, see where the gaps are, and decide what to build next. By the end of the day, you know what's missing.

We build it live. You'll see the second agent come together in half the time the first one took. The OS is doing the work. Then we walk through everyone's Playbook draft.

The compound-interest moment. Until now your agents have run when you asked. Today they run on their own: a morning brief that arrives at 7am, a meeting prep that fires when a new event lands on your calendar, a weekly report that writes itself on Friday. You'll learn what to automate first, what to keep manual, and how humans stay in the loop.

A polished output can still be a bad output. You'll learn how to tell whether your agents are actually doing the job: what's useful, what's missing, what's wrong, what's risky. The review loop becomes the habit that keeps your Agent OS sharp.

Tighten the Playbook. Sharpen the agents. Pick the two or three things you'll show. You'll prepare a five-minute demo: what you built, what changed in your week, what you'd build next.

We will give everyone the chance to demonstrate their work.