workflow-skill-designer

To generate a multi-phase workflow skill, define your orchestration requirements and phase conditions. The designer outputs a structured skill package with a coordinator SKILL.md and phase documents managing conditional execution, inter-phase data flow, and progressive loading.

The orchestrator-plus-phases pattern separates workflow coordination from execution using a central SKILL.md coordinator to route phases and collect preferences, while individual phase files execute specific tasks. This structure ensures safe, consistent multi-step execution.

Progressive phase loading uses YAML frontmatter for skill discovery and Ref markers in SKILL.md to link phase documents. This ensures phase contents load on-demand only when referenced, keeping the orchestrator lightweight and execution efficient.

Yes, you can collect interactive workflow preferences upfront in SKILL.md using AskUserQuestion. This preference-safe design keeps phase files focused strictly on execution, free from argument flag parsing and inter-phase routing logic.

You validate structural integrity and reference consistency by running the dedicated validation phase included in the generated skill package. It checks YAML frontmatter, Ref-based reference integrity, data-flow consistency across phases, and overall phase hygiene constraints.

Avoid the orchestrator-plus-phases workflow design for simple, single-step tasks lacking conditional phases, inter-phase data flow, or upfront preference collection. The structural overhead provides no benefit without multi-step orchestration requirements.