Workflow Create¶

Create a new workflow unit (DAG + step instructions). Use this instead of docs_create for kind='workflow' units — docs_create does not accept workflow-specific fields.

MCP name: workflow_create

Category: context

Mutates state (retry policy: manual)

Parameters¶

Name	Type	Required	Description
`aliases`	`str`	No	Comma-separated search aliases
`allow_override`	`bool`	No	Allow per-step execution override (default false)
`command`	`str`	No	Slash command name (e.g. 'wb-dev-document')
`content_full`	`str`	No	Workflow-level context (philosophy, what-not-to-do). Surfaces at depth='full'.
`content_summary`	`str`	No	One-paragraph summary.
`description`	`str`	Yes	One-line summary
`dev_notes`	`str`	No	Dev-mode-only notes about the workflow's internals
`execution`	`str`	No	Default execution policy: 'main' or 'subagent' (default 'main')
`name`	`str`	Yes	Human-readable name
`params_schema`	`str`	No	Optional JSON object declaring caller-provided initial params: {param_name: {type, description, required}}. Mirrors capability parameters. Workflows that omit this reject any non-empty params at start.
`parents`	`str`	No	Comma-separated parent paths (typical: domain, e.g. 'dev')
`path`	`str`	Yes	Unique path ID (e.g. 'dev/dev-document')
`step_instructions`	`str`	No	JSON object mapping step_id -> instruction text. Reasoning steps generally need this; pure auto_run steps usually don't.
`steps`	`str`	Yes	JSON array of step dicts. Each step requires at least id, name, step_type ('reasoning' or 'code'), and depends_on (list of prior step ids). Additional keys: auto_run, visibility, result_schema, invokes, optional.
`tags`	`str`	No	Comma-separated search tags
`workflow_name`	`str`	Yes	Registry slug used with `wb_run('<workflow_name>')`