workflow-creator

Workflow Creator

Treat the workflow as a saved directed acyclic graph:

• each node is one execution step
• each edge is one allowed transition
• branching belongs on edges, not inside node instructions

Authoring Rules

• Treat recurring automation, scheduled execution, and reusable procedures as workflow-authoring tasks, not graph-only tasks.
• Before calling create_workflow, execute the requested task manually once with the concrete user inputs or the closest accessible substitute.
• For non-trivial reusable logic, create or update a skill or script before saving the workflow so the repeated behavior lives in one deterministic place.
• End-to-end verification is required before saving the workflow. Brief or shallow checks are not enough.
• Finalize the full graph before calling create_workflow.
• Keep workflow_name to a DNS label up to 32 characters, for example repo-triage.
• Keep each node.name unique and in the same DNS-label format.
• Ensure the graph is connected and acyclic.
• Ensure the graph has at least one start node and one terminal node.
• Keep node instructions concrete. Each node must define instructions, goal, and done_criteria.
• Add preferred_skills when a node should load specific OpenCode skills before execution.
• Add preferred_tools only when it gives real execution guidance.

Input Schema Rules

• Omit inputs and arbitrary_json when the workflow takes no parameters.
• Use exactly one input contract: either typed inputs or arbitrary_json, never both.
• Use arbitrary_json when the workflow should accept one free-form JSON payload. Its allowed fields are description and default_payload.
• arbitrary_json.default_payload is a prefill example, not a runtime fallback.
• When present, inputs must be a flat object keyed by input name.
• Each input must be a schema object with at least type and required.
• Supported input types are scalar only: string, integer, number, boolean.
• Allowed input keys are: type, description, required, default, enum, minLength, maxLength, pattern, format, minimum, maximum, exclusiveMinimum, exclusiveMaximum, multipleOf.
• Put required inside each input schema object. Do not use top-level JSON Schema required arrays inside one input definition.
• Do not use nested object or array schemas.
• Do not include extra JSON Schema metadata such as $schema, title, properties, items, additionalProperties, oneOf, anyOf, or allOf.
• Workflow definition inputs declare the schema only. Runtime workflow inputs are separate JSON values validated against that schema later.