build-plugin

# Build Plugin Bundle many tools (skills, hooks, agents, MCP servers) into one installable Claude Code plugin and distribute it. The defining move of this skill: establish who the plugin is for and where it will live with `AskUserQuestion` before assembling anything, then tailor every phase to that answer. A personal one-project bundle and a public team marketplace share almost nothing past "assemble", so branch early and commit to the branch. ## How this relates to build-mcp `build-mcp` builds one MCP server: analyze a service, implement the tools, deploy, scale. `build-plugin` bundles many tools (including MCP servers produced by `build-mcp`) into a single shareable unit and distributes it. When `build-mcp` reaches its Distribute phase for a team or public audience, it hands off here: packaging into a plugin and listing it on a marketplace is this skill's job. Use `build-mcp` to make a server, then `build-plugin` to ship it alongside your skills, hooks, and agents. ## The four phases 1. **Analyze**: decide what tools go in the bundle, and name it. 2. **Assemble**: build the plugin folder and manifest, test it locally with `claude --plugin-dir`. 3. **Ship**: put it on a marketplace repo, on the right git host, public or private, with one-click enablement for a team. 4. **Maintain**: versions, updates, ownership, and admin controls. Run them in order. The `AskUserQuestion` answers from Phase 0 gate Ship and Maintain. ## Phase 0: Establish context (AskUserQuestion, do t...