create-pluginlisted

Follow the `create-plugin` skill workflow to scaffold a new Claude Code plugin. ## Inputs - `$ARGUMENTS` — optional plugin name in kebab-case. Omit to start with discovery. ## Steps 1. If `$ARGUMENTS` provides a plugin name, use it to seed Phase 1 2. Follow the create-plugin phased workflow: discover purpose and plugin type, plan component table (skills / commands / agents / hooks / MCP), ask clarifying questions per component, scaffold directory structure and `plugin.json`, implement each component using the appropriate sub-skill, validate, test, and document 3. **plugin.json Binding Check (MANDATORY — do not skip):** After every skill, agent, command, and hook is scaffolded: - Read `.claude-plugin/plugin.json`. - Verify each generated skill directory appears in the `skills` list. - Verify each agent file appears in the `agents` list. - Verify each command file appears in the `commands` list. - Verify each hook appears in the `hooks` list. - Add any missing entries immediately — do NOT wait for the user to ask. - Report: *"All components are registered in `plugin.json`. ✅"* or list additions made. 4. **plugin.yaml (Hermes compatibility — always generate):** After `plugin.json` is finalized, scaffold a `plugin.yaml` at the plugin root for hermes-agent compatibility. Format: ```yaml name: <plugin-name> version: <version> description: "<description>" author: <author> kind: backend # or standalone (no Python scripts) platfo