Frame mid-delivery clarifying questions
Turns an execution-time ambiguity — a definition, exception, or edge case needed to interpret data correctly — into one or a few concise, answerable questions for the client.
In / outExecution ambiguity + step context → concise clarifying question(s) for the client
You might say…
“I'd make an interpretation call and later find out I'd guessed wrong — framing the question cleanly upfront saves rework and keeps the client in the loop.”
What it does
Turns an ambiguity surfaced during execution — a definition, exception, or edge case needed to interpret data correctly — into one or a few concise, answerable questions for the client. Used when a diagnostic step cannot proceed until a factual clarification is resolved.
Trigger: Use when a diagnostic step cannot proceed until a factual clarification is resolved; provide the ambiguity and its impact on the current step.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation