skill-design

To design plugin skills with clear dependencies, enumerate plugin capabilities, define single-responsibility skill boundaries with verb-noun names, and map required data-flow connections to produce a structured skill map.

Skill decomposition in plugin architecture is the process of breaking a plugin idea into implementable units by defining interfaces, inputs, outputs, and complexity tiers to guide build order and prevent scope creep.

Map data-flow dependencies for workspace planning by reading domain references and existing skill implementations, then charting required versus optional connections to establish a recommended build order for your plugin.

Assess complexity tiers for domain modeling tasks by classifying each decomposed skill into Simple, Moderate, Script-heavy, or MCP-dependent categories to accurately guide implementation effort and resource allocation.

Yes, you need event-storm planning artifacts and domain-model outputs beforehand, because skill design reads these workspace domain references to identify domain responsibilities and workflows before decomposing capabilities.

Prevent scope creep when defining plugin interfaces by explicitly specifying out-of-scope elements and preconditions for each skill, ensuring single-responsibility boundaries are maintained throughout the plugin architecture.