/ask
Usage
/ask <decision to put to D>
Also triggers without the slash: "ask me…", "get my input on…", "check with me before…", or any moment a decision is D's to make and plain-text questions would go unanswered.
Description
The question primitive. D answers decisions through the AskUserQuestion dialog, not prose — the dialog takes
focus immediately, so anything load-bearing that sits in prose above it goes unread. This skill defines the one
question format every D-facing ask uses; /interview and /process-linear both build on it.
Exception: process-linear's decision table
/process-linear renders its D-decisions as a two-tier table instead of one dialog per decision — a table row IS
the ask, satisfying "every question to D through AskUserQuestion." The dialog still fires on drill-in: D asks for
more on a row, a decision needs structured options or an artifact preview, or a D1/D2 cohort needs its per-cohort
irreversibility confirm (see that skill's step 7 for the exact triggers — a fired dialog still follows this skill's
format). This is the only sanctioned substitute for the dialog; no other skill swaps it for prose.
Expected Output
User: ask me which auth approach to use
Claude: (AskUserQuestion dialog)
Ask: Which auth approach for the API?
[JWT (Recommended) — matches the existing session model]
[OAuth2] [API keys]
User: (picks JWT)
Claude: Going with JWT — wiring it into the middleware now.
Behavior
One decision per question
Ask exactly one thing. A dialog may carry up to 4 questions only when they are tightly-related facets of the
same decision — unrelated decisions never share a dialog. Use multiSelect when the choices are not mutually
exclusive.
Question format
All decision-relevant context lives inside the dialog. The scaffold is context-adaptive:
Warm (the subject is already live in this conversation): just the ask.
Ask: Which naming scheme for the new module?Cold (the subject arrives fresh — a ticket, an alert, a new topic): full scaffold, each part 1-2 short lines, never a run-on paragraph of inlined figures and IDs:
<headline — what this is about, verbatim title if it has one> Context: <what this is, in plain words — no digging required> Latest: <the most recent material update, dated> Why it matters: <consequence of this decision> Ask: <exactly ONE clear question>
Options
- 2-4 concrete options; tag exactly one "(Recommended)" with a one-line rationale in its description. The recommendation comes from judgment of the conversation — never present a bare menu with no lean.
- Option
previewpanes carry artifacts only — exact message copy, a diff summary, the dollar math a choice would enact. A preview that re-narrates context D already has is noise. - Don't spend option slots on "skip"/"other" — the dialog always lets D type a custom answer.
After the answer
Act on it. If the answer changes something recorded elsewhere (a ticket, a doc), write the decision where it belongs before moving on.
Notes
/interviewis the looped form of this skill — rounds of/ask-format questions until zero doubts remain.- If D's answer challenges the premise of the question, treat that as the real answer — don't re-ask.