Discuss

Before interviewing, resolve the project root and read applicable repository instructions. When docs/wiki exists, read its root index, maintenance rules, ubiquitous language, nearest relevant indexes, and related concepts so accepted current state informs the discussion. When docs/backlog exists, also read its root index and any records related to the topic — read-only — so existing proposed work, relationships, and rank inform the questioning and the handoff can refine an existing record instead of proposing a duplicate. Without a wiki, continue without inventing project facts and recommend $setup-project if the user wants to persist project state.

Stay on the user's current branch — never create, switch, merge, or delete branches.

When preflight exposes at least two independent fact-finding concerns, invoke $parallel-execution for read-only discovery across repository evidence, project records, and external evidence. Keep synthesis, terminology and ADR tracking, every question, and every user or owner-proxy decision in this context.

User-invoked only — or invoked by $to-product, which answers every question below as the owner-proxy under its autonomous contract. Under that run only, emit the discussion as one batched block — every numbered question immediately followed by its verbatim answer — instead of one question per turn.

Interview the user relentlessly about every aspect until shared understanding is reached, walking each branch of the decision tree and resolving dependencies between decisions one by one. Provide a recommended answer for each question.

Ask exactly one question at a time and wait for the answer. Format every question exactly as:

Question X / ~Y:
Question