elicitlisted

# Elicit — form-driven Socratic discovery **IMPORTANT: Start your response by telling the user:** > **Elicit** — Gathering the independent dimensions of your decision > as one form (multi-select where it fits), instead of asking one > button at a time. This skill turns a **declarative form** (data, not code) into a real `AskUserQuestion` turn and validates the answers. It is the live wiring of `attune.elicitation` via two MCP tools: - `elicitation_render_form` — validate the form, get batched payloads. - `elicitation_collect_response` — validate the answers (R4). ## When to render a multi-field form (the batching rule) Batch 2–4 fields into **one** form-turn only when ALL hold: - the fields are **independent dimensions of one decision** the user makes together (e.g. spec kickoff: goal + scope + focus), AND - answers **don't branch** on each other (if a field's relevance depends on another's answer, stay sequential), AND - each field is **genuinely ambiguous** — a dimension the user already specified is omitted, not asked. **Stay single-question** when only one dimension is unknown, a later question depends on an earlier answer, or batching would feel like a bureaucratic intake for a simple ask. The form never adds fields the ordinary Socratic-ambiguity judgement wouldn't already ask. ## Step 0 — check the template library first (V7) Recurring fork classes are stored as named JSON templates in the `attune_forms` package (`attune_forms/templates/` in the install