statuslisted

# /requivo:status Report where a session stands. This is a **deterministic read** — do not re-analyse the request with Claude; just run the command and translate the result. ## Preflight This is often the first Requivo command a new user runs, and the `requivo` CLI is a **separate install** from the plugin. So start with the shared **preflight** in `${CLAUDE_PLUGIN_ROOT}/REASONING.md`: run `requivo doctor --json` and check whether the command ran *at all* — not what it reported. If it could not run, the CLI is not installed; follow REASONING.md's missing-CLI flow. This skill reads and writes nothing, so there is nothing to undo. ## Resolve the session `$ARGUMENTS` may already be a session slug. If it is empty, or you are not sure, resolve one the same way `/requivo:run` does: run `requivo session list --json` once and pick a slug from its `sessions` rows — exactly one `readable: true` row → that one; more than one → the one with the latest `updated_at` (name the others you did not pick); none at all → say there is no session yet and point at `/requivo:run` instead of running `status`. **Never ask the user to type a slug.** ## Run With a slug in hand, run: ``` requivo status <slug> --json ``` (Add nothing else — the numbers come from Core, not from you.) ## Relay Translate the JSON into plain language, in the vocabulary the user reads elsewhere — *what we know*, *what we are assuming*, *open question*, *needs updating*. Slot ids are the wire format, not something to show: