The fourteen plugins
Twelve knowledge-work domain plugins plus two specialized coworkers — each an installable Claude plugin (
plugins/cwc-*, registered in the repo's.claude-plugin/marketplace.json) that is the operating model for the ~50-domain subagent*.com fleet. Skills and MCPs iterate per domain, the way cwc-design set the pattern.
Anthropic defines the primitive this whole page rests on: plugins "bundle MCP connectors, skills, slash commands, and sub-agents into a single shareable unit — turning Claude into a specialist tailored to your role, team, and company" (claude.com/docs/plugins/overview, this site's grounding document). The fourteen rows below are fourteen instantiations of that sentence.
Every plugin follows the same anatomy (command, skills, sub-agent, gates), states its side effects in gates.toml, and operates a real fleet surface. This table is generated from the actual plugin manifests, not maintained by hand.
| Plugin | Kind | Command | Skills | Gates | MCP |
|---|---|---|---|---|---|
| cwc-bio-research | domain | /bio-research |
bio-research-scoping |
none — read-only by design | no |
| cwc-customer-support | domain | /support |
support-playbook |
task_write |
no |
| cwc-data | domain | /data |
data-playbook |
none — read-only by design | no |
| cwc-design | domain | /design |
design-playbook, architecture-wireframes |
publish, wireframe_retire |
yes |
| cwc-engineering | domain | /engineering |
engineering-playbook |
git_push, agent_yaml_regen_commit, schema_change |
yes |
| cwc-finance | domain | /finance |
spend-tracking, monetization-gateway |
spend_commit, enrollment_submit, pricing_rule_write |
no |
| cwc-human-resources | domain | /human-resources |
agent-workforce |
model_tier_change, identity_register |
no |
| cwc-legal | domain | /legal |
compliance-playbook |
external_send, publish_page |
no |
| cwc-marketing | domain | /marketing |
content-and-discoverability |
content_publish, content_signal_change |
no |
| cwc-operations | domain | /operations |
fleet-operations, fleet-audit |
bulk_primitive_write, zone_dns_change |
no |
| cwc-product-management | domain | /brand |
brand-voice |
guideline_write |
no |
| cwc-sales | domain | /sales |
pipeline-playbook |
outreach_send, external_contact, ledger_write |
no |
| cwc-deploy | specialized | /deploy |
deploy-playbook |
deploy, secret_put |
no |
| cwc-analytics-engineer | specialized | /analytics |
analytics-playbook |
snapshot_write, graphql_query_beyond_given |
no |
How a domain iterates
cwc-design is the pattern: it began with one skill (design-playbook, the 8-token buddy loop) and grew a second (architecture-wireframes, CRUD on the family's Figma/FigJam architecture set) when the fleet needed one — same plugin, new skill, no new infrastructure. Each domain plugin is the durable home for its function's skills and MCP wiring; adding capability to a domain means adding a skill file to its plugin, not standing up a new system.
Where the plugins show up in the fleet
- Each plugin has a registered identity on subagentidentities.com (
surface: macos_claude_code, one row per coworker, with its gate summary asaccess_scope) and the routing rule is a durable directive row there — the claude-tag instruction-layers model applied to this repo. - The operates edges on subagentdevices.com/architecture draw each plugin against the fleet surface its skills read or write — the in-fleet, design-token rendering of this roster.
- The role taxonomy records how the original nine-role RFC maps onto these twelve domains, and architecture wireframes documents the Figma co-editing surface.
2176021028ee2859 · verify