Adding a Plugin

A new plugin makes sense when a coherent set of skills, rules, agents, or templates doesn’t fit any V1 plugin’s scope — typically a vertical (FSI / HLS / PubSec compliance overlays) or a new domain (security tooling, data engineering, MLOps).

Steps

Pick a name. Kebab-case, prefixed acn-. Plugins are addressed as <plugin>:<skill> so the prefix keeps invocations distinguishable from user-scope skills.
Create a feature branch.
Terminal window
```
git checkout -b feat/<plugin-name>
```
Scaffold the plugin directory. At minimum:
```
plugins/<plugin>/
  .claude-plugin/
    plugin.json
  skills/  OR  rules/  OR  agents/  OR  commands/  OR  hooks/
```
At least one of skills/, rules/, agents/, commands/, or hooks/ must exist — a plugin with only a manifest does nothing.

Write plugin.json. Required fields: name, version, description, author, keywords. See Plugin Manifest Schema for the full spec.

{
  "name": "acn-<plugin>",
  "version": "0.1.0",
  "description": "One-sentence summary visible in /plugins list.",
  "author": {
    "name": "Your name",
    "email": "your.email@accenture.com"
  },
  "keywords": ["domain", "audience", "acn"]
}

Add at least one skill, rule, or agent. Follow the per-artifact flow:
- Skills → Adding a Skill
- Rules → drop a markdown file into rules/<topic>.md
- Agents → drop a markdown file into agents/<name>.md with frontmatter (model, tools, color)
Register in the marketplace. Edit .claude-plugin/marketplace.json and add an entry in alphabetical order by name (CI checks this once V1.5 validators ship):
```
{ "name": "acn-<plugin>", "source": "./plugins/acn-<plugin>" }
```

Validate locally.

claude plugin validate ./plugins/<plugin>
claude plugin validate .                  # marketplace manifest

Smoke-test.
Terminal window
```
claude --plugin-dir ./plugins/<plugin>
```
Update the claude-acn shell function in pilot onboarding so pilot users load the new plugin by default.
Open a PR. CI runs validation. Platform-team approval, merge.

What goes in a plugin vs. a separate marketplace

If the new domain is broad enough to host multiple plugins (e.g., a whole HLS toolkit with patient-data, regulatory-comms, and clinical-trial sub-plugins), a separate marketplace repo may make more sense long-term. For V1, every plugin lives in this single marketplace; revisit if the catalog grows past ~10 plugins.

Reference plugins

Plugin	Shape
`acn-base-sdlc`	4 skills + 5 rules + 3 agents — a “core utility” plugin
`acn-pursuit-toolkit`	2 skills + 2 rules + 1 agent + 3 templates — a workflow-driven plugin
`acn-slide-gen`	1 skill + 2 flavors + 3 helper scripts — an asset-heavy plugin with bundled scripts