create-plugin
Guided workflow for creating a Claude Code plugin: design the components, implement them and validate the result.
- Kind
- Prompt
- Works with
- Claude Code
- Source
- anthropics/claude-plugins-official @ 58267944f921
- Path
- plugins/plugin-dev/commands/create-plugin.md
- Jobs
- Planning, Implementation, Testing
Credit
- Made by
- anthropics
- Original
- github.com/anthropics/claude-plugins-official/blob/58267944f9…
- License
- Apache-2.0
Listed by Skill Manifest; not made by us.
InstallInstall it from a plugin marketplace.
/plugin install plugin-dev@claude-plugins-official
Install factsScanned 2 Nov 2026
- Adds
- .claude/commands/create-plugin.md (run as /create-plugin)
- Runs scripts
- Yes
- allowed-tools includes Bash
- shell block in the text
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- 58267944f921
- Licence
- Apache-2.0
- Last activity
- 1 Nov 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
# Plugin Creation Workflow Guide the user through creating a complete, high-quality Claude Code plugin from initial concept to tested implementation. Follow a systematic approach: understand requirements, design components, clarify details, implement following best practices, validate, and test. ## Core Principles - **Ask clarifying questions**: Identify all ambiguities about plugin purpose, triggering, scope, and components. Ask specific, concrete questions rather than making assumptions. Wait for user answers before proceeding with implementation. - **Load relevant skills**: Use the Skill tool to load plugin-dev skills when needed (plugin-structure, hook-development, agent-development, etc.) - **Use specialized agents**: Leverage agent-creator, plugin-validator, and skill-reviewer agents for AI-assisted development - **Follow best practices**: Apply patterns from plugin-dev's own implementation - **Progressive disclosure**: Create lean skills with references/examples - **Use TodoWrite**: Track all progress throughout all phases **Initial request:** $ARGUMENTS --- ## Phase 1: Discovery **Goal**: Understand what plugin needs to be built and what problem it solves …