generate-steps

To generate a workflow YAML skeleton, provide a baseline idea or existing workflow structure. The skill outputs a structural WorkflowDefinition containing steps, transitions, and triggers without execution configuration, enabling safe ideation and machine validation.

Yes, you can modify an existing workflow structure. The skill alters your baseline WorkflowDefinition while preserving unchanged parts, outputting only the updated steps, transitions, and triggers needed for later augmentation with executor configurations.

A structural WorkflowDefinition schema subset is used to define automation steps, transitions, and triggers before execution. It enforces machine-parseable YAML validation to ensure executable definitions without embedding premature execution configurations.

No, the generated workflow YAML does not include execution configuration. It outputs only the structural skeleton of steps, transitions, and triggers, making it suitable for safe handoff to an execution proposal generator for later augmentation.

The best way to sketch workflow transitions and triggers is by generating a structural YAML subset. This approach separates structural ideation from execution config, ensuring your baseline workflow definitions are machine-parseable and ready for downstream refinement.

Workflow YAML schema validation fails if the structure deviates from the required structural subset of the WorkflowDefinition schema. The skill enforces this subset to ensure your steps, transitions, and triggers remain machine-parseable and structurally executable.