status-checklisted

# /status-check > **Distinct from `/sync-status`.** `/sync-status` reconciles the tracker against `plans/phases.yaml` (is a phase ready to gate? any orphan issues?). `/status-check` shows live *orchestrator runtime* state — which workers are running right now, what's claimed, what's stuck. When in doubt: "what can I gate?" → `/sync-status`; "where am I right now?" → `/status-check`. Read-only cockpit for driving one or many parallel orchestrator sessions. Answers the cold-start question: *I just sat down — what's running, what's stuck, what can I pick up?* Works standalone — no `/forge orchestrate` dispatch loop required. ## Steps 1. **Run the dashboard verb (one call, read-only).** ```bash forge orchestrate dashboard --json ``` In this dev repo (where the globally-installed `forge` binary may lag the source), use the dev entry instead: ```bash node --import tsx src/bin/forge.ts orchestrate dashboard --json ``` The verb prints a `{ ok, data }` envelope. `data` has: `active_sessions`, `open_questions`, `ready_tasks`, `blocked_tasks`, `overlap_warnings`, `lease_health`, `source`, and `warnings`. It never mutates state and degrades gracefully (empty `ready_tasks`/`blocked_tasks` + `source.ready_blocked: "unavailable"` when `phases.yaml` is missing). 2. **Render a human summary** grouped into four panels: - **Active workers** — each `active_sessions[]` run with its `claimed_tasks`. - **Open questions** — each `open_questions[]` as `[<question_id