What problem does it solve?
Building a Kandev runtime plugin requires coordinating a dedicated repository, a manifest, a Go pluginsdk executable, optional UI bundles, and marketplace publishing rules, and mistakes in any step produce broken or unpublishable artifacts.
Core Features & Use Cases
- Repository Resolution and Setup: Locates the owning plugin repository for bug fixes or bootstraps a new one from the kdlbs/kandev-plugin-template with synchronized manifest id, Go module, and release naming.
- Contract-Grounded Implementation: Enforces the authoritative hook, Host API, capability, and manifest contracts from the public authoring docs, pluginsdk, and gRPC proto before writing code.
- Artifact Verification and Publishing: Packages the tarball, smoke tests it on a disposable Kandev instance across lifecycle, events, webhooks, and UI, then guides release tagging and marketplace catalog submission.
- Use Case: A developer asked to fix a bug in an existing Kandev plugin uses this Skill to resolve the correct plugin repository, reproduce and fix the issue there, rebuild the package, and verify the artifact on a disposable instance before release.
Quick Start
Create a new Kandev plugin called kandev-plugin-slack that reacts to task events and package it for a dev instance.