generate-execution-proposals

To generate execution proposals, provide an approved workflow structure with steps and transitions. The skill discovers available plugins via the platform API and outputs multiple complete WorkflowDefinition objects, enriching every step with executor, plugin, agent, autonomyLevel, and env fields.

Workflow execution proposals are complete WorkflowDefinition objects that turn an approved workflow structure into executable definitions. You need them when you have a workflow design without executor information and must evaluate different automation strategies for governance and cost constraints.

Yes, you can compare manual, hybrid, and full-auto automation strategies. The skill generates one to multiple proposals for an approved workflow, allowing you to evaluate trade-offs between speed, cost, and safety for use cases like pharma workflows.

No, the skill does not require executor information in the input. It takes an approved workflow structure containing steps, transitions, and triggers, then discovers available execution plugins to enrich the structure with the missing executor and plugin fields.

The best way to turn a workflow structure into an executable definition is using a skill that discovers available plugins and generates enriched WorkflowDefinition objects. This approach automatically populates executor, plugin, agent, autonomyLevel, and env fields on every step.

A key limitation is dependency on the platform API for plugin discovery; unavailable or restricted plugins limit the generated proposals. Additionally, the skill requires a fully approved workflow structure with defined steps and transitions as input to function correctly.