answerlisted

# /requivo:answer Refine an existing session with the user's answers. **You** reason; Requivo Core validates and applies. Read `${CLAUDE_PLUGIN_ROOT}/REASONING.md` first. ## 0. Preflight Run the shared **preflight** from REASONING.md before anything else: `requivo doctor --json`, checking whether the command ran *at all* rather than what it reported. If it could not run, the `requivo` CLI is not installed — say the four things REASONING.md lists and stop. This is before any mutation, so the session is exactly as the user left it. ## 1. Load the session `$ARGUMENTS` is the session slug (and, optionally, the answers). Run: ``` requivo model show <slug> # the current model requivo status <slug> --json # the open questions / blockers, and the current revision requivo context --session <slug> # the same cards the model was built against ``` Read the context by session, not with a bare `requivo context`: the selection is part of the session, and refining a model against a wider set than it was built on shifts the impact estimates underneath it. Note the `revision` from the status JSON — call it `N`. That is the model you are about to reason from, and you will state it when you apply (see the revision contract in REASONING.md). If you don't already have the user's answers in the conversation, present the still-open questions and **wait** for them. Never fabricate answers. Waiting is exactly when the session is most likely to move under you, which is what `--expe