Continuously interview the user until a shared understanding is reached. Draw it as a tree of design tree: each decision branches into the decisions that depend on it.
Traverse this tree by rounds .Frontier is all decisions whose prerequisites are already determined, that is, the questions that can be asked now without guessing answers that have not yet been heard. In each round, ask about the entire frontier: number each question and provide a recommended answer, then wait for the user to answer before starting the next round.
The user's answers in each round reshape this tree: decisions that have been determined push the frontier outward and unlock the questions that depend on them. Recompute the frontier, then ask the next round. If a question depends on another question that is still unresolved in this round, leave it forsubsequentrounds, rather than placing it in this round.
Finding facts is your job, never the user's job. If a question on the frontier needs facts from the environment (filesystem, tools, etc.), dispatch a sub-agent to find them; do not ask the user anything you can look up yourself. Do not block the whole round because of this: an exploration still running is an unresolved prerequisite, and only the questions that depend on it need to wait for the sub-agent to report back; ask the other questions on the frontier now.Decisions belongs to the user—hand them to the user one by one and wait for answers.
The session ends only when the frontier is empty: every branch of the design tree has been visited, and no assumption has been silently left behind. Do not take action before the user confirms that a shared understanding has been reached.