Role taxonomy
Twelve domain coworkers plus eight specialized ones, each an installable Claude plugin scoped to least-privilege tools for its domain. Organized to mirror Anthropic's own knowledge-work-plugins domain set — so skills and MCPs can be maintained and iterated per domain.
This taxonomy was originally nine roles (the table this page carried until 2026-07-02, from the platform RFC). It was reorganized to the twelve knowledge-work domains when Anthropic's plugin set expanded to cover them (eleven plugins launched 2026-01-30; design, engineering, human-resources, and operations added February 2026). The nine-role RFC maps cleanly onto the twelve: product and project management merged into one plugin, and bio-research, customer-support, and marketing were absent from the RFC entirely. Both facts are stated here rather than silently renumbered.
The twelve domain plugins
| Coworker | Owns | Hard rule / gate |
|---|---|---|
| Bio-research | Nothing yet — an honest placeholder; gatekeeps bio-adjacent requests until a real use case exists | — |
| Customer-support | Triage against live health checks, curl-repro before answering, evidence-bearing bug tasks | Triage and reads open; task writes gated |
| Data | Warehouse (D1, Kimball-style facts and dimensions), semantic-layer-first SQL | Read-only by default |
| Design | 8-token design system, WCAG contrast lint, buddy character packs, and the family's Figma/FigJam architecture-wireframe set (CRUD, token-styled) | Publish requires the two-phase buddy gate; retiring a wireframe board is operator-gated |
| Engineering | TypeScript/Rust implementation, the typed agent schema (crates/schema → agent-gen), scaffolding new workers from the template | Git push, schema changes, and agent regeneration commits gated; builds what deploy ships |
| Finance | Cost tracking, vendor spend, and the content-monetization playbook (Cloudflare Monetization Gateway, x402, USDC/OUSD) | Spend gated before any cost is incurred; enrollments and pricing rules gated |
| Human Resources | The agent workforce: hiring is a role row + typed agent definition + identity registration; review is rubric-graded evaluation; comp is model-tier assignment | Model-tier changes and identity registration gated |
| Legal | Compliance of what the fleet republishes, license hygiene, monetization-enrollment terms | Never sends or publishes externally without operator approval |
| Marketing | Content and discoverability for agent traffic: llms.txt, Content-Signal, sitemap, API catalog, on-brand copy | Content publishes and Content-Signal changes gated |
| Operations | The day-to-day operating loop (contract-first definition of done → durable tasks → route → rubric-graded outcomes → weekly review) and fleet audits | Bulk primitive writes and zone/DNS changes gated |
| Product Management | Brand voice as durable, sourced guidelines; roadmap and outcomes | Guideline writes gated |
| Sales | Durable prospect/opportunity ledger, qualification of inbound API interest | Outreach never sent without operator approval |
The eight specialized coworkers
| Coworker | Owns |
|---|---|
| Deploy | The full Cloudflare Worker ship path: install, typecheck, wrangler deploy, D1, secrets, curl-verify. Every domain plugin routes deploys here. |
| Analytics-engineering | Provenance-tagged Cloudflare analytics snapshots — never originates a GraphQL query beyond exactly what's given. |
| Agent-resources | HR for the AI workforce — coworker lifecycle (recruit, onboard, evaluate, grow, dissolve), org design, and policy. |
| Data-engineering | The session-telemetry ERD and the durable data spine — Kimball fact_/dim_ modeling over the Task primitive, JSONL→SQLite pipelines with cross-language parity. |
| Hardware-engineering | Apple device hardware and the device-management surfaces enterprises actually use (sysctl, devicectl, profiles, system_profiler); every fact provenance-tagged. |
| iOS-engineering | The fleet's Apple surface, above and below: Swift/SwiftUI apps on the house ClaudeAPI module, plus Linux systems engineering on Apple silicon via Apple's container runtime. |
| Swift-engineering | The Swift language/package/framework surface — the house ClaudeAPI client, SwiftPM graphs, and the shared cross-language wire shape (CodingKeys mirror serde/Pydantic/Zod). |
| Xcode-engineering | The Xcode toolchain and the xcrun-driven build/sign/simulate/distribute surface; distribution is operator-gated. |
Plugin anatomy (as actually shipped)
plugins/cwc-<domain>/
├── .claude-plugin/plugin.json # marketplace metadata
├── commands/<domain>.md # /<domain> entry point
├── skills/<name>/SKILL.md # the domain's playbooks (one or more)
├── agents/<domain>-coworker.md # sub-agent definition (markdown, least-privilege tools)
├── mcp/servers.json # per-role MCP wiring (only where a real binary exists)
└── gates.toml # approval policy
All twenty are registered in the repo's .claude-plugin/marketplace.json. (The RFC's original
sketch showed mcp/server.toml and generated agents/*.yaml; the shipped convention across all
twenty plugins is mcp/servers.json and markdown agent definitions — the generated-YAML system
lives at the repo level in .claude/agents/, produced by crates/agent-gen.)
Related
- How it works
- Approval gates
- Architecture wireframes — the Figma board that draws this page
- Getting started — installing a
cwc-*plugin
648edfa1b8fed35c · verify