Getting started

Installing a coworker is installing a Claude plugin — no separate account, no separate deploy, just a marketplace add.

Installation is Cowork's own mechanism, not a custom installer: "Add packaged skills, connectors, and agents to Cowork from the plugin marketplace or a file" (claude.com/docs/cowork/guide/plugins). A coworker is a plugin; the marketplace is this repo's .claude-plugin/marketplace.json.

Install a role

claude plugin install cwc-design@subagentjobs

installs the design coworker: its slash command (/cwc-design), its playbook skill, its generated least-privilege agent, and its gates.toml. Engineering, data, and the other roles install the same way once published.

What you get immediately

• A /cwc-<role> entry point that claims tasks from that role's queue
• An MCP server scoped to exactly the tools that role needs — nothing borrowed from another role
• A gate policy, if the role has one — Legal and Finance ship gated by default

What you don't have to build

The e2m envelope, the DurableTask state machine, the a2a peer-messaging bus, and the buddy approval surface are shared infrastructure — a new role binds to them, it doesn't reimplement them. Adding a tenth coworker is adding a RoleConfig table entry and a plugin directory, not a new protocol.

See it live

coworkers.subagentknowledge.com is the running 7-coworker directory — the same roles described here, deployed.

Related

• Role taxonomy
• How it works