Plugin Architecture¶

The toolkit is organized into independent plugins that can be selectively installed per team or department.

How plugins work¶

A plugin is a directory inside plugins/ that contains agents, skills, commands, and optionally hooks. Each plugin has a plugin.json that declares its metadata and components.

plugins/
├── registry.json                  # Declares all available plugins
├── core-standards/                # Required base plugin
│   ├── .claude-plugin/
│   │   ├── plugin.json
│   │   ├── skill-symlinks.manifest
│   │   ├── command-symlinks.manifest
│   │   └── hook-symlinks.manifest
│   ├── agents/
│   ├── skills/
│   ├── commands/
│   ├── hooks/
│   └── scripts/
└── finance/                       # Optional department plugin
    ├── .claude-plugin/
    │   ├── plugin.json
    │   └── skill-symlinks.manifest
    ├── skills/
    ├── agents/
    └── commands/

Plugin registry¶

The plugins/registry.json file declares all available plugins:

{
  "plugins": {
    "core-standards": {
      "path": "plugins/core-standards",
      "required": true,
      "version": "3.0.0"
    },
    "finance": {
      "path": "plugins/finance",
      "required": false,
      "version": "1.0.0",
      "depends_on": ["core-standards"]
    }
  }
}

Core standards plugin¶

The core-standards plugin is required and provides:

All 7 orchestrators
All 3 workflows (Development, Product Design, Knowledge Work)
Security hooks (secret scanning, security lint)
Core review agents
The complete learning loop (journal, consolidate, compound)

Every other plugin depends on core-standards.

Department plugins¶

Department plugins add domain-specific capabilities on top of the core:

Plugin	Example skills	For
`finance`	financial-reporting, budget-planning, compliance-sox	Finance team
`support`	ticket-triage, customer-response, escalation-workflow	Support team
`marketing`	content-calendar, campaign-brief, brand-voice	Marketing team

Department plugins can include:

Skills — domain knowledge and workflows
Agents — specialized reviewers or researchers
Commands — entry points into department workflows
Hooks — optional domain-specific quality gates

Dependencies¶

Department plugins declare their dependencies in plugin.json:

{
  "name": "finance",
  "version": "1.0.0",
  "depends_on": ["core-standards"],
  "description": "Financial reporting and compliance skills"
}

When installing a department plugin, setup.sh automatically installs its dependencies.

Installation model¶

Each plugin carries its own manifest files that define what gets symlinked:

skill-symlinks.manifest — maps skill names to SKILL.md files
command-symlinks.manifest — maps command names to command files
hook-symlinks.manifest — maps hook scripts (optional)

The setup.sh script reads these manifests and creates the appropriate symlinks in ~/.claude/.

Creating your own plugin¶

See Creating Plugins for a step-by-step guide.