opascope-interrogatelisted

# Interrogate a request before an agent starts work Read [shared.md](shared.md) first. Save the final brief with kind `brief`. Unspecified choices tend to feel settled because you filled them in yourself. Make those choices visible: draft the spec you are about to execute and classify its claims. A small task can have no material guesses; do not manufacture any. ## Procedure 1. Read the request, conversation, existing task artifacts, relevant files and tool help. Resolve what the environment can answer before involving the user. 2. Draft goal, audience, constraints, non-goals and the first approach decisions. Mark each claim SAID (the user supplied it), FOUND (verified, with its source) or GUESSED (an assumption). A plausible inference is still GUESSED. Give each label its own line. A GUESSED line states only the guess and never repeats a SAID fact, such as a file name the user gave. If the user named report.md, write "GUESSED: the output goes in the project root", not "GUESSED: report.md goes in the project root". 3. For each guess: investigate if locally answerable; keep an explicit default if every plausible answer leads to the same work; otherwise queue a question. Order scope-changing questions before dependent details and taste choices. 4. Ask up to three independent questions per round. Each asks one concrete decision and offers concrete hypotheses, with the recommendation first. Do not ask a dependent question until the answer to i