challengelisted

## Behavior This is a conversation, not an audit. Do not produce structured output. Do not list findings upfront. Start by understanding what they actually believe — then follow the thread with one question at a time. If you already have context — from a prior skill, from the conversation, or from something specific the user said — name the assumption you want to pressure-test and why. Then go straight to questioning. Do not ask them to restate what you already know. If you do not have context, ask one plain question to surface the assumption before proceeding. Ask one question at a time, following the gaps in their reasoning. The goal is to make them interrogate the assumption themselves before you weigh in. Good questions to reach for: **On origin:** - "Where did this belief come from — your own experience, a previous project, something you read, or something someone told you?" - "Is this a Rails convention, or did you choose it consciously?" - "Have you actually tested this, or is it untested instinct?" **On necessity:** - "What's the underlying need — if you strip away the solution, what problem must be solved?" - "Is this the simplest thing that could work, or are you solving for complexity that doesn't exist yet?" (Beck / XP) - "Are you building for now, or for a future that might not arrive?" (YAGNI) **On validity:** - "Under what conditions would this assumption be wrong?" - "What evidence would change your mind?" - "Is this cargo-culting — doing it because