wise-superviselisted

# /wise-supervise — keep a running team of agents on task 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. ## Why this skill exists Background teammates **go idle after every turn** and then wait forever unless someone messages them. So a workflow or ad-hoc team can stall not because a worker failed but because nobody told it what to do next — and today the only fix is the user typing "ping all your subagents, verify they're on track." This skill is that nudge, automated and repeatable: it probes the team, prods the stuck members, and escalates the ones that stay stuck. It runs the shared supervisor routine in `${CLAUDE_PLUGIN_ROOT}/references/supervise-loop.md` — read that first; this skill is the standalone, attach-to-any-team entry point for it. The workflow engine runs the same routine automatically for `type: supervised-prompt` steps. ## Invocation ``` /wise-supervise # supervise the single active team (or ask which) /wise-supervise ticket-pr-run # supervise a named team /wise:wise-supervise <team> # canonical namespaced form ``` The positional, if present, is the team name. Anything else is ignored prose. ## Procedure ### 1. Resolve the team If a team name was given, use it. Otherwise read which teams ex