Interview me about the important unresolved aspects of this idea, plan, ticket, epic, or draft until we reach enough shared understanding for a strong handoff into PRD creation and implementation.

Do not grill relentlessly. Do not optimize for exhausting every open question. Optimize for asking the minimum worthwhile HITL questions needed to clarify product shape, UX, architecture, contracts, major technical choices, scope, risk, and project direction.

Ask the questions one at a time, waiting for feedback on each question before continuing.

If a question can be answered by exploring the codebase or documentation, explore first instead of asking.

Before asking, identify the ambiguity yourself. Do not ask me meta-questions about what needs clarification, what docs should be written, or how work should be sequenced.

Every question must include:

A short explanation of why the question matters
A recommended answer
A short 1-2 sentence rationale for that recommendation grounded in the ticket, docs, codebase, or stated goals

Ask only questions that are worthwhile for the HITL to answer. Prefer questions about:

clarify-with-docs