Chief Of Staff Kit

chief-of-staff-kit

One chief of staff for Claude Code and Codex. It is a single main loop that
plans the work, does the work and keeps the context. Your divisions and crafts are
skills it opens when it needs them, three helpers run in their own window
when a separate context changes the result, hooks hold the actions you never
want taken without a yes, and golden tasks, run for you in a test mode where
nothing is sent or changed, tell you whether a change helped. A short interview
fits all of it to your work. No two installs look the same.

Explore the live system

Open the live, read-only BluPlai whiteboard
to explore the native, editable release workflow from the private AIOS to the public
kit. It needs no BluPlai account, and changes to the board appear there live.

What you get

A division is whatever unit you run: a business, a department, a team, a
product line, a client book, or a person you manage. Each one becomes a skill:
the main loop sees a one-line summary and opens the full file (facts, people,
voice, filing, open work) only when the work touches it.

Why one loop

Up to v0.5.0 this kit installed an org chart: a chief of staff that routed to a
lead per division, and leads that pulled in specialists. Every hop was a
hand-off, and hand-offs drop decisions. In the author's own use, the generic
helpers, forks and the code reviewer did almost all of the delegated work; the
named division leads were almost never called.

Anthropic's article *Building agents: When to fold subagents into your main
agent loop*
(22 October 2026) names the same failure modes in larger systems: context lost
at each hand-off, subagent sprawl, the "Frankenprompt" of conflicting rules,
evals that test one piece only, and latency (one customer's single loop ran
roughly twice as fast).…