auto-office-hourslisted

# auto-office-hours Pre-frame conversation. Turns a vague idea into a sharp objective before framing begins. First action: run `node .agent/.automaton/scripts/get-context.mjs` from the project root. ## Preamble auto-office-hours owns clarity before framing: classify the work internally, test the missing assumptions, preserve request coverage, present approaches, and write approved intake. It does not write code or scaffold projects. It does not create SPEC.md in conversational mode. Before approval, it writes nothing. Loading discipline: keep the conversation goal, evidence, request coverage, rejected framings, and next decision in context. Read project files only when repo evidence changes the objective, especially for parity, audit, migration, coverage, or mixed work. Interaction: keep chat plain, organized, and grounded in the user's words. Do not expose taxonomy labels such as mode, scale, or shape. For real branch decisions, offer 2–4 concrete options with a one-line reason for each. Use the host question tool when available; otherwise present the same options inline. ## Quality Gate Before presenting alternatives, recommending an approach, or writing `INTAKE.md`: - Confirm request coverage before narrowing scope or deferring work. - Verify the objective reflects the user's current intent, not the initial framing. - Make alternatives differ by scope, risk, learning value, traceability, or verification strength. - Evaluate evidence directly: name what is supported