Wise Workflow Status

---
name: wise-workflow-status
description: >-
  Show workflow runs on the wise engine. With no argument, list every
  run with its status, workflow, start time, cwd and live children.
  With a run ULID, show that run; when it is gated, show the gate and
  offer to answer it. Invoked as `/wise-workflow-status` (bare alias) or
  `/wise:wise-workflow-status` (canonical). Use when the user says "list
  workflow runs", "show workflow status", "status of my workflow",
  "which runs are paused", "inspect run <ulid>", or types
  `/wise-workflow-status`.
argument-hint: "[<run-ulid>]"
allowed-tools: Read, AskUserQuestion, Bash(bash:*), Bash(python3:*), Bash(test:*)
---

# /wise-workflow-status

Preferred model: `opus`; preferred effort: `low`. Resolve availability before work;
do not silently substitute.

Before executing, follow [model fallback](../../references/workflow-host-control.md#model-fallback)
for unavailable models or delegation routes, including in autonomous procedures.

At every skill start, identify your main/child role and the current client
and GUI/TUI question tools, then 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.


`wise_status` comes from the managed `wise-engine` MCP server. On
`DAEMON_UNAVAILABLE`, follow host-control diagnostics before retrying.

## No argument

`wise_status {}` returns `RunSummary[]`, newest activity first. Render
one table: run id | workflow | status | started | cwd | children. The
children column lists each live child as `<step> turn <n> <tool>`, or
`-`. Empty list: `No engine runs yet.` If legacy history is requested,
  get the canonical root with
  `python3 "${WISE_PLUGIN_ROOT}/scripts/wise-helpers.py" runs-root`,
  then use that helper's `list-runs <root>` command. It reports v1
  entries as read-only legacy notices; they cannot resume. Keep all
  history files unchanged.

## With a run id

`wise_status {run_id}` returns one `RunSummary`. Print run id,
workflow, status, started, last activity, completed (when set), cwd,
children as above. `RUN_NOT_FOUND`: `No run <run_id>.`

Status `gated`: print `gate.step` and `gate.message`, then
AskUserQuestion `Answer this gate now?` with the gate's options plus
`Not now` (free text when `allow_text`); beyond the host's option cap
follow the
[long option list rule](../../references/workflow-host-control.md#long-option-lists)
so every gate option stays reachable. On a choice, `wise_answer
{run_id, gate_id, value}`, print `gate answered`, point to
`/wise-workflow-resume <run_id>` to follow the run.

## Rules

- Read-only apart from the offered gate answer.
- Do not invoke other wise skills.