wise-workflow-runlisted

# /wise-workflow-run — the conductor ## Why this skill exists Running a workflow is an orchestration task: parsing a DAG, tracking per-step state, driving parallel executions, asking for approvals, and surfacing progress. This skill owns that loop. Together with `wise-workflow-resume`, it is one of only two skills in the plugin allowed to invoke other wise action skills (as part of `type: skill` steps from a validated workflow definition) — see the invariant documented in `CLAUDE.md`. ## Arguments Read `$ARGUMENTS`. The first whitespace-separated token is the `workflow-name`; everything after it is **positional input values** for the workflow's declared `inputs:` (see [§2](#2-resolve-the-workflow-name) and [§6c](#6c-collect-workflow-inputs)). When `$ARGUMENTS` is empty, the skill prompts interactively in [§2](#2-resolve-the-workflow-name). - `workflow-name` — matches the filename without `.yaml`. Resolution order: user dir first, bundled second. When absent, [§2](#2-resolve-the-workflow-name) prompts the user to pick from the available definitions. - positional inputs — optional. Tokens after the workflow name are assigned to the declared inputs **in order**, and the **last declared input absorbs the entire remainder of the line** (verbatim, spaces preserved) so a trailing free-form prompt works. An input satisfied positionally is **not** prompted for in §6c. Example: `/wise-workflow-run ticket-auto PROJ-1 prefer the wise-estimation skill; never touch inf