Most people begin with one long system prompt. It knows the company, the clients, the writing style, the product architecture, the calendar, the sales process and every exception that has accumulated over six months. Eventually it becomes less like a capable colleague and more like a shared inbox nobody owns.
My answer was not to write an even longer prompt. It was to design an organisation.
What is the chief-of-staff kit?
The chief-of-staff kit installs a customisable team of AI agents for Claude Code and Codex. You get one orchestrator at the front, a lead for each business or division you run, and a shared bench of specialists behind them.
The chief of staff does the triage. A request about a client proposal goes to the right business lead, which can pull in a presentation writer, product designer or commercial problem solver. A website launch can combine the web builder, growth marketer and code auditor. Email and knowledge agents are opt-in because they touch systems that deserve a deliberate permission boundary.
Frames the brief, assigns ownership and synthesises one answer.
Architect · code auditor · programme manager · problem solver · presentation writer · growth marketer · product designer · content engine · web builder · video editor · operations steward · knowledge and communications agents
The installer does not assume your company looks like mine. It reads your existing project instructions, asks what divisions you actually operate and renders the team around your context. The names are the least important part. The operating doctrine is the product: explicit ownership, bounded delegation, generator-and-reviewer pairing, and one decisive synthesis instead of a menu of half-compatible answers.
What changed in v0.2?
The July release closes the gap between a good starter kit and a system you can keep. It adds a safe updater for people who already installed an earlier crew, native Codex custom agents, four new production specialists and an Advisor adoption runbook.
Update without throwing away your context
If you have already taught an agent who your customers are, how you write and which tools you trust, replacing its file wholesale is the wrong migration strategy. The updater inventories the crew already installed, shows the proposed changes, makes scoped backups and preserves your divisions and workspace rules before it writes.
/plugin marketplace update skyremote
/plugin update chief-of-staff-kit@skyremote
/reload-plugins
/chief-of-staff-kit:update-crewUse the same people in Codex
The same personas can now render as native Codex agents under .codex/agents/ or ~/.codex/agents/, with a root AGENTS.md that explains when delegation is actually useful. This matters because an agent system should travel with the way you work; it should not trap its operating model inside one interface.
Add Advisor as a deliberate decision layer
The new Advisor runbook helps you adopt Anthropic's Advisor primitive without confusing it with the whole crew. The crew owns ongoing roles and delivery. Advisor is most useful as a bounded second opinion around a decision, with a clear question, evidence and an explicit verification step.
/chief-of-staff-kit:advisorHow do you install it from scratch?
Add the marketplace, install the plugin, restart Claude Code and tell it to install the crew. The interview takes a few minutes; the result is written as plain files you can inspect, edit and version.
/plugin marketplace add skyremote/chief-of-staff-kit
/plugin install chief-of-staff-kit@skyremote
Then: install the crewNothing about this needs to remain mysterious. The repository is MIT licensed. Fork it, change the roles, remove what you do not need and make the operating model fit your organisation.
Open source · v0.2.0
Build an organisation, not a mega-prompt.
Install the crew, inspect every file and keep your own operating context when the kit moves forward.