# Bounded README production interview

## When to ask

There is no mandatory interview. Ask only when two plausible answers would materially change scope, architecture, permissions, accessibility, or visual direction. For README work, a material choice may affect the audience and required content, whether the deliverable includes original artwork or only factual Markdown, an accessible static-versus-motion treatment, an authorized output location, or a publication boundary. Do not ask about a preference already settled by the request, repository evidence, an applicable instruction, or an earlier answer.

When the brief already bounds the work, state the default and proceed. Use repository evidence and established identity for defaults; state assumptions that materially affect the result. Do not pause for a ceremonial approval of a bounded brief.

If a brief lists competing visual directions and leaves them undecided, that choice is still open: calling each option "acceptable" is not a choice or a delegation. Ask it in a separate round after higher-impact questions are answered; you may recommend one option in the question, but do not declare a default for it or start building until the user chooses. A brief that gives no visual direction at all is different: follow established identity or the default cover direction without asking. Defaults cover only what the brief settles, what it explicitly hands to you, and details that do not materially change the result.

## How to ask

Ask one high-impact question at a time, in one turn. Present the distinct alternatives that change the deliverable and name their practical effect. Do not combine unrelated decisions into a questionnaire or ask the user to repeat the brief. Wait for the answer before asking about another unresolved material choice. Continue for as many rounds as materially necessary, and stop once remaining choices can safely follow stated defaults.

Retain earlier answers across rounds in the conversation and the task-local direction note. On resume, reread confirmed choices and inspect partial work before asking anything new. Do not re-ask a resolved question. An answer narrows the requested work; it does not grant broader file, host, credential, network, or publication authority.

Review, plan, and keyword-only requests remain read-only. Do not use production questions to turn them into an asset or README edit. If the user cancels, stop new writes and record partial status; a later resumption reuses confirmed facts and assets.