create

/plugin-dev:create — Plugin Scaffolding

Scaffold a new Claude Code plugin in the cc-skills marketplace.

Step 1: Plugin Name

If $ARGUMENTS is provided and matches kebab-case (^[a-z0-9-]+$), use it as the plugin name.

Otherwise, ask the user:

AskUserQuestion: "What should the plugin be named? (kebab-case, e.g. my-plugin)"

Validate:

• Must match ^[a-z0-9-]+$
• Must NOT already exist in .claude-plugin/marketplace.json (check plugins[].name)
• Must NOT have an existing directory at plugins/<name>/

If invalid, explain why and ask again.

Step 2: Category

Ask the user to pick a category from the marketplace schema enum:

AskUserQuestion: "Which category?"
Options: code-review, development, productivity, quality, automation, documentation, devops, utilities

Step 3: Components

Ask the user which components to include (multi-select):

AskUserQuestion: "Which components does your plugin need?" (multiSelect: true)
Options:
- skills — SKILL.md definitions (triggers, allowed-tools)
- hooks — Pre/PostToolUse, SessionStart hooks
- commands — Slash commands (/plugin:command)
- agents — Agent/subagent definitions

At least one must be selected. If none selected, default to skills.

Step 4: Create Directory Structure

Create the plugin directory with selected components:

plugins/<name>/
├── skills/<name>/SKILL.md    (if skills selected)
├── hooks/hooks.json           (if hooks selected)
├── hooks/placeholder.sh       (if hooks selected)
├── commands/                   (if commands selected — empty, user fills in)
├── agents/                     (if agents selected — empty, user fills in)
├── README.md
└── LICENSE

Generated SKILL.md (if skills selected)

---
name: <plugin-name>
description: "<one-line description — user should update>"
allowed-tools: [Read, Bash, Grep, Glob]
user-invocable: true
---

# <Plugin Name>

TODO: Describe what this skill does and when it triggers.

Generated hooks.json (if hooks selected)