interview-me

# Interview Me Use this before `/spec-driven-development`, `/spec`, or `/plan` when the requested outcome is not clear enough to implement without guessing. ## When To Use Use when the ask is missing one or more of: - Who the user/operator is - Why this matters now - What success looks like - The binding constraint or tradeoff - Explicit out-of-scope boundaries Skip for mechanical edits, obvious bug fixes, pure information requests, or when the user explicitly asks for speed over clarification. ## Process ### 1. State A Hypothesis Write one sentence plus a confidence number. ```text HYPOTHESIS: You want workspace switching to preserve task context because agents lose momentum when users navigate between workspaces. CONFIDENCE: 45% - missing: who feels the pain, what "preserve" means, and what counts as done. ``` ### 2. Ask Focused Questions Format every question with a guess. ```text Q: Is this primarily for human users switching between workspaces, or for office agents operating across workspaces? GUESS: Human users, because the pain sounds navigation-related rather than automation-related. ``` If the active harness provides a native user-question UI that supports multiple questions in one turn, ask 2-4 focused questions together. Keep each question short, include your guess in the prompt or options, and make the options concrete enough that the user can answer quickly. If no multi-question tool is available, ask one question at a time in chat. Do not send a lon...