michalatt Look at where the conversation is right now. Pick 1-2 questions from the banks below — only the ones that actually matter for this moment. Then answer each one you picked. Be direct and specific to what we're discussing.
Never pick more than 2. If in doubt between two questions, pick the harder one.
If the conversation doesn't have enough substance to give a specific, non-obvious answer — say so in one line instead of forcing an answer.
Question bank
| # | Question | When to pick it |
|---|---|---|
| 1 | What's the simplest version of this? | Scope is growing, features are stacking, or we're designing something that could be smaller |
| 2 | What am I not asking that I should be? | About to commit to a direction — pick this to surface blind spots before we lock in |
| 3 | What would someone who disagrees say? | We're both excited about an idea and haven't stress-tested it |
| 4 | Explain it like I need to decide, not understand | The conversation has gotten theoretical, too many details, or Claude is over-explaining |
| 5 | What would you do differently if you started over? | Deep into implementation and might be stuck on a path because of sunk cost |
If ${CLAUDE_SKILL_DIR}/custom-questions.md exists, include those questions in the bank too. Custom questions follow the same format: question + when to pick it.
How to respond
For each question you pick:
- State the question as a heading
- Answer it in 2-4 sentences, specific to the current conversation
- No disclaimers, no "great question" — just the answer