fix

Fix (guided intake)

IMPORTANT: Start your response by telling the user:

Fix — Composing an outcome-first fix: goal, scope, and verification probes, then a preview before anything runs.

What It Does

Interactive intake for attune fix (the outcome-first Fix surface, docs/specs/outcome-first-fix/): one form gathers the goal, the --scope the diff must stay confined to, and the --probe commands that verify the fix — with scope and probe options DERIVED from the working tree (changed paths and matching test files), not typed from memory. The composed CLI command is previewed before any execution; the receipt independently verifies every probe.

Relationship to /fix-test: that skill diagnoses and fixes a FAILING TEST in-session. This skill drives the attune fix CLI contract — goal + scope + probes + receipt — for any code fix. Neither replaces the other.

Step 1 — Derive candidates and build the form

python -m attune.elicitation.fix_intake

The JSON payload contains a validated form definition (attune.elicitation.fix_intake.build_fix_intake_form) plus the derived scopes and probes lists. Changed paths lead; on a clean tree the candidates fall back to recently-touched directories from git history, so pickers render in either state — empty lists mean the repo has no usable history at all. If the user's invocation already stated the goal, carry it into the request field as the default rather than asking again.

Step 2 — Render the form (communication grammar)

Render ONE form — request, scope, probes. The enhanced widget is the DEFAULT surface: build the FormSchema from the Step 1 payload, route it through select_form_surface, and when it returns "widget" render form_to_widget_html(form) on the widget surface — answers post back as an __elicitation_response__ payload; parse them with collect_form_response. Carry an already-stated goal into the request field as its default.

Fall back to AskUserQuestion ONLY when no widget surface exists (batch the questions; metadata.source containing "form" opts into the batch). Never ask these as sequential single questions — and never hand-write the ask turn without consulting select_form_surface first: steering that names the fallback concretely gets the fallback executed. When a field came back with no derived options it is free text — accept a path or command, do not invent options.