statuslisted

# $status — Workflow Dashboard > **Purpose:** Single-screen overview of your current state. What am I working on? What happened recently? What should I do next? **YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.** **CLI dependencies:** bd, ao, gt — all optional. Shows what's available, skips what isn't. --- ## Quick Start ```bash $status # Full dashboard $status --json # Machine-readable JSON output ``` --- ## Codex Lifecycle Guard When this skill runs in Codex hookless mode (`CODEX_THREAD_ID` is set or `CODEX_INTERNAL_ORIGINATOR_OVERRIDE` is `Codex Desktop`), ensure startup context before gathering the dashboard: ```bash ao codex ensure-start 2>/dev/null || true ``` `ao codex ensure-start` is the single startup guard for Codex skills. It records startup once per thread and skips duplicate startup automatically. Leave `ao codex ensure-stop` to dedicated closeout skills such as `$validation`, `$post-mortem`, or `$handoff`. --- ## Execution Steps ### Step 1: Gather State (Parallel) Run ALL of the following in parallel bash calls for speed: **Call 1 — RPI + Ratchet + Task State:** ```bash # Current ratchet phase if [ -f .agents/ao/chain.jsonl ]; then tail -1 .agents/ao/chain.jsonl 2>/dev/null else echo "NO_CHAIN" fi # Ratchet status via CLI if command -v ao &>/dev/null; then ao ratchet status --json 2>/dev/null || echo "RATCHET_UNAVAILABLE" ao task-status --json 2>/dev/null || echo "TASK_STATUS_UNAVAILABLE" fi ``` **Call 2 — B