create-kandev-plugin

# Create Kandev Plugin Build Kandev runtime plugins from the official template and current public contracts. Keep plugin source outside the Kandev monorepo and prove the packaged artifact against a disposable development instance before publishing it. Start with the [canonical plugin authoring guide](../../../docs/public/plugins-authoring.md). Use this skill for the repository workflow after choosing a recipe there: choose recipe → edit manifest → implement → validate → package → smoke test. The guide owns the complete hook/Host matrix; this skill keeps the repository and verification procedure concise. ## Establish The Boundary 1. Invoke this skill only when the user intends to create, change, fix, test, package, release, or submit a Kandev runtime plugin. A passing mention of plugins, a generic extension request, or the presence of plugin host code in the Kandev monorepo is not sufficient. 2. Confirm the artifact: a Kandev runtime plugin ships a `manifest.yaml`, a platform executable built with the Go `pluginsdk`, and optionally a native UI bundle. Agent instruction packages, MCP servers, and other products that also use the word "plugin" are outside this skill. 3. Classify the work as a new plugin, an existing plugin change, a Kandev host or SDK dependency required by the plugin, or a marketplace-only change. 4. Keep each production plugin in one dedicated repository. For an official plugin, use a public `kdlbs/kandev-plugin-<slug>` repository. ...