fix: mandate AskUserQuestion for all exploration questions
All questioning workflows now require AskUserQuestion tool for every question, not just decision gates. Inline text questions are prohibited. Updated: questioning.md, new-project.md, discuss-phase.md, discuss-milestone.md, and their workflow files. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -9,68 +9,113 @@ The user often has a fuzzy idea. Your job is to help them sharpen it. Ask questi
|
||||
Don't interrogate. Collaborate.
|
||||
</philosophy>
|
||||
|
||||
<conversation_arc>
|
||||
**1. Open:** "What do you want to build?"
|
||||
<critical_rule>
|
||||
**ALL questions MUST use AskUserQuestion.**
|
||||
|
||||
Let them talk. Don't interrupt with clarifying questions yet.
|
||||
Never ask questions inline as plain text. Every exploration question uses the AskUserQuestion tool with thoughtful options that help the user articulate their vision.
|
||||
|
||||
This applies to:
|
||||
- Opening questions ("What do you want to build?")
|
||||
- Follow-up questions ("You mentioned X — what would that look like?")
|
||||
- Sharpening questions ("What's essential vs nice-to-have?")
|
||||
- Boundary questions ("What's out of scope?")
|
||||
- Decision gates ("Ready to proceed?")
|
||||
|
||||
The AskUserQuestion format helps users think by presenting concrete options to react to, rather than facing a blank text field.
|
||||
</critical_rule>
|
||||
|
||||
<conversation_arc>
|
||||
**1. Open**
|
||||
|
||||
Use AskUserQuestion:
|
||||
- header: "Vision"
|
||||
- question: "What do you want to build?"
|
||||
- options: Contextual starting points if available, otherwise broad categories + "Let me describe it"
|
||||
|
||||
Let them respond. Then follow up based on what they said.
|
||||
|
||||
**2. Follow the thread**
|
||||
|
||||
Whatever they said — dig into it. What excited them? What problem sparked this? Follow their energy, not a checklist.
|
||||
Whatever they said — dig into it. What excited them? What problem sparked this?
|
||||
|
||||
"You mentioned [X] — what would that actually look like?"
|
||||
"When you imagine using this, what happens?"
|
||||
Use AskUserQuestion with options that probe what they mentioned:
|
||||
- header: "[Topic they mentioned]"
|
||||
- question: "You mentioned [X] — what would that actually look like?"
|
||||
- options: 2-3 interpretations of what they might mean + "Something else"
|
||||
|
||||
**3. Sharpen the core**
|
||||
|
||||
Help them distinguish the essential from the nice-to-have.
|
||||
|
||||
"If you could only have one thing working, what would it be?"
|
||||
"What's the simplest version that would make you happy?"
|
||||
Use AskUserQuestion:
|
||||
- header: "Core"
|
||||
- question: "If you could only nail one thing, what would it be?"
|
||||
- options: Key features/aspects they've mentioned + "All equally important" + "Something else"
|
||||
|
||||
**4. Find the boundaries**
|
||||
|
||||
What is this NOT? Explicit exclusions prevent scope creep later.
|
||||
|
||||
"What are you specifically NOT building in v1?"
|
||||
"Where does this stop?"
|
||||
Use AskUserQuestion:
|
||||
- header: "Scope"
|
||||
- question: "What's explicitly NOT in v1?"
|
||||
- options: Things that might be tempting to include + "Nothing specific" + "Let me list them"
|
||||
|
||||
**5. Ground in reality**
|
||||
|
||||
Only ask about constraints that actually exist. Don't invent concerns.
|
||||
|
||||
"Any hard constraints — tech stack you must use, deadline, platform requirements?"
|
||||
"Does this need to work with anything existing?"
|
||||
Use AskUserQuestion:
|
||||
- header: "Constraints"
|
||||
- question: "Any hard constraints?"
|
||||
- options: Common constraint types relevant to context + "None" + "Yes, let me explain"
|
||||
</conversation_arc>
|
||||
|
||||
<good_vs_bad>
|
||||
**BAD — Interrogation mode:**
|
||||
- "What is your target audience?" (form field)
|
||||
- "What are your success criteria?" (corporate speak)
|
||||
- "Have you done X before?" (irrelevant — Claude builds)
|
||||
- "What's your budget?" (asked before understanding the idea)
|
||||
**BAD — Inline text questions:**
|
||||
- Asking "What is your target audience?" as plain text
|
||||
- Free-form "Tell me more about X" without options
|
||||
- Any question that leaves the user staring at a blank input
|
||||
|
||||
**GOOD — Thinking partner mode:**
|
||||
- "You said [X] — do you mean [interpretation A] or more like [interpretation B]?"
|
||||
- "What would make you actually use this vs abandoning it?"
|
||||
- "That's ambitious — what's the core that matters most?"
|
||||
- "Is [Y] essential or just how you're imagining it currently?"
|
||||
**GOOD — AskUserQuestion with options:**
|
||||
- header: "Audience"
|
||||
- question: "Who is this for?"
|
||||
- options: ["Just me", "My team", "Public users", "Let me describe"]
|
||||
|
||||
**BAD — Corporate speak:**
|
||||
- "What are your success criteria?"
|
||||
- "What's your budget?"
|
||||
- "Have you done X before?" (irrelevant — Claude builds)
|
||||
|
||||
**GOOD — Concrete options that help them think:**
|
||||
- header: "Done"
|
||||
- question: "How will you know this is working?"
|
||||
- options: ["I'm using it daily", "Specific metric improves", "Replaces current workflow", "Let me describe"]
|
||||
|
||||
**BAD — Checklist walking:**
|
||||
- Ask about audience → ask about constraints → ask about tech stack (regardless of what user said)
|
||||
|
||||
**GOOD — Following threads:**
|
||||
- User mentions frustration with current tools → dig into what specifically frustrates them → that reveals the core value prop → then explore how they'd know it's working
|
||||
**GOOD — Following threads with targeted options:**
|
||||
- User mentions frustration → AskUserQuestion with specific frustration interpretations as options → their selection reveals the core value prop
|
||||
</good_vs_bad>
|
||||
|
||||
<probing_techniques>
|
||||
When answers are vague, don't accept them. Probe:
|
||||
When answers are vague, don't accept them. Probe with AskUserQuestion:
|
||||
|
||||
**"Make it good" → "What does good mean to you? Fast? Beautiful? Simple?"**
|
||||
**"Make it good"** →
|
||||
- header: "Good"
|
||||
- question: "What does 'good' mean here?"
|
||||
- options: ["Fast", "Beautiful", "Simple", "Reliable", "Let me describe"]
|
||||
|
||||
**"Users" → "Which users? You? Your team? A specific type of person?"**
|
||||
**"Users"** →
|
||||
- header: "Users"
|
||||
- question: "Which users?"
|
||||
- options: ["Just me", "My team", "Specific type of person", "Let me describe"]
|
||||
|
||||
**"It should be easy to use" → "Easy how? Fewer clicks? No learning curve? Works on mobile?"**
|
||||
**"It should be easy to use"** →
|
||||
- header: "Easy"
|
||||
- question: "Easy how?"
|
||||
- options: ["Fewer clicks", "No learning curve", "Works on mobile", "Let me describe"]
|
||||
|
||||
Specifics are everything. Vague in = vague out.
|
||||
</probing_techniques>
|
||||
|
||||
Reference in New Issue
Block a user