How to set up a team OS for AI agents

Short answer: a team OS is the shared layer a team runs its work on: a memory everyone reads from, skills anyone can run by name, agents with one job each, and loops that run on a schedule. You set it up one workflow at a time, starting with the work the team repeats every week.

Why a team needs one

Most teams adopt AI one person at a time. Each person builds private prompts, gets private results, and none of it compounds. When someone leaves, their setup leaves with them.

A team OS makes the work shared. A skill one person writes on Monday, everyone runs on Tuesday.

The four parts

• Memory. Decisions, definitions and playbooks in one place, in plain files that people and agents both read.
• Skills. A skill is a repeatable task written down once: the steps, the inputs, the standard for done. "Write the weekly status" is a skill. So is "review a contract against our policy".
• Agents. Each agent has a narrow job, a named human owner and access to only the tools it needs.
• Loops. Work that runs on a schedule without being asked: a morning inbox check, a weekly metrics report, a nightly data check.

Set it up in five steps

1. List what the team repeats. Status reports, review checklists, data pulls, handoffs. Pick the three that cost the most hours.
2. Write each as a skill. One page: when to use it, the steps, what a good result looks like. Have the person who does it best write it.
3. Put the memory under version control. A shared repository works. Everyone can read it, changes are reviewed, and history is kept.
4. Add one loop. Take the most boring recurring task and schedule it. Give it a stop rule: if the output fails a check, it does not publish.
5. Name an owner for every agent and loop. If nobody owns it, it rots.

Rules that keep it healthy

Keep a registry: every loop, what it does, who owns it, when it last ran. A loop that returns nothing and reports success is the most common failure, so check for empty results explicitly.

Never let a loop post on someone's behalf without a person approving it. Drafts are cheap. A wrong message sent to a customer is not.

What to expect

The first skill takes a day to write. By the tenth, new ones take an hour, because they reuse the memory and the earlier skills. That reuse is the point of calling it an operating system.