requivo-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. ## 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 ``` 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. ## 2. Reason → propose the refinement Start from the current model. For each slot the answers touch: raise `completeness`, flip `inferred` → `explicit` where the client confirmed it, and update `value`. Leave untouched slots as they are. Keep **every** required slot present. Add follow-up `questions` only where information value is still high; emit `[]` when nothing is both uncertain and high-impact (discovery has converged). Pass the client's answers through faithfully — do not embellish them. Write the full updated model to `/tmp/requivo-proposal.json`. ## 3. Validate → fix → apply ``` requivo model validate /tmp/requivo-proposal.json --json requivo model apply <slug> /tmp/requivo-proposal.json --json ``` Fix and re-validate on any error before applying (see REASONING.md). ## 4. Relay the result From the `model apply` JSON, tell the user in plain language: - which slots changed, - any **decisions to re-validate** (`invalidated_decisions`)