What problem does it solve? Designing a DSH plugin without upfront decisions leads to wrong plugin forms, missing dependencies, broken profile patches, and rework. This Skill turns a requested capability into explicit, validated package decisions before any files are created. ## Core Features & Use Cases - Plugin Form Selection: Decides between function plugins (named exports with inject/Config/apply) and service plugins (default-exported Service subclass), avoiding Loader unwrapping pitfalls. - Dependency & Configuration Matrix: Records every imported DSH service with availability, Cordis access pattern, manifest entries, and fail-loud validation rules for each config field. - Lifecycle, Invariant & Test Planning: Defines ownership of registrations, timers, and watchers, designs the ./invariant companion export, plans profile composition rows, and selects the minimal evidence tiers. - Use Case: When asked to add a new capability to DSH, use this Skill to produce a complete handoff for dsh-plugin-development covering pluginForm, roles, dependency matrix, configuration, lifecycle, invariant, bundle rows, test tiers, and distribution assumptions. ## Quick Start Use dsh-plugin-plan to design a standalone DSH plugin for my requested capability, deciding its form, dependencies, configuration, invariant, profile composition, and test plan before writing any code.
