wise-workflow-createlisted

# /wise-workflow-create - author a v2 workflow Before asking any user question, read and follow the [question lifecycle](../../references/workflow-host-control.md#keep-asynchronous-questions-open). Keep asynchronous prompts open until answered; this rule does not authorize questions in autonomous or otherwise prompt-free procedures. First read [host control](../../references/workflow-host-control.md). Resolve the loaded installation, set `WISE_HOST` to this conductor and `WISE_PLUGIN_ROOT` to that installation. Use its managed launcher for shell commands. Follow the reference's diagnostics and explicit-answer fallback when MCP or a native picker is unavailable. Conductor host and child provider are independent. Create `version: 2` definitions for the Python engine. Use the host's structured picker for choices and text inputs. Keep accepted answers across stages; never create v1 `prompt`, `loop`, or `interactive` steps. ## 1. Resolve the destination Run the init check in `${WISE_PLUGIN_ROOT}/references/init-check.md`, then read canonical roots and existing definitions: ```bash "$HOME/.local/share/wise/bin/wise-engine" --wise-host "$WISE_HOST" definition-roots "$HOME/.local/share/wise/bin/wise-engine" --wise-host "$WISE_HOST" list-defs ``` The first argument is the workflow name. Ask for it if absent; require `^[a-z][a-z0-9]*(-[a-z0-9]+)*$`. Reject an existing name in either root, including flat `<name>.yaml` and folder `<name>/workflow.yaml` forms. Never overwrite an e