yassimba/loom/grill-me

Interview the user relentlessly until you reach a shared understanding. Map this as a design tree: every decision branches into the decisions that hang off it.

The frontier is every decision whose prerequisites are already settled: the questions you can ask _now_ without guessing at answers you haven't heard yet. Work the frontier one question at a time. A question whose answer depends on another question still open belongs later, not now.

Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.

Format each question like so:

❓ **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
 
➡️ <your recommended answer>

Each answer reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next question.

Finding _facts_ is your job, never the user's. When a question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it; don't ask the user for anything you could look up yourself. The _decisions_ are the user's: put each to them and wait.

Before the first question, check whether the discussion will define project-specific domain language or settle an enduring architectural decision. If so, read references/domain-modeling.md and follow it during the session. Otherwise keep the session conversational and create no domain docs.

The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.