mblauberg Grill me
Interview the highest-leverage unresolved branch first. Resolve dependent decisions one at a time; do not exhaustively interrogate low-value detail. For each question, give the evidence already known, 2–3 concrete options when useful, and a recommended answer with its trade-off.
Before recording scope or stories, apply engineering-docs's repository-process
route. If no unambiguous owner exists, return the proposed register in chat;
writing a tracker needs explicit external-write authority.
Keep the explicit decision context current: intake/revision, constraints, evidence, decided branches, parked owner calls and the next unresolved branch. Do not start a parallel interview when revising the same request.
Ask one question at a time. Record decided, parked and still-open branches in
the enclosing scope artifact when write authority exists; otherwise keep a
compact chat register.
If a question can be answered from the workspace or current authoritative
sources, investigate it instead of spending user attention. Stop when the
shared decision/acceptance contract is clear, the user asks to stop, or the next
branch needs unavailable owner authority. Return the resolved register to
scope for a digest-bound handoff; the interview itself is not approval.
Portable artifact
Use the skill-owned decision context schema.