interview-me

# Interview Me Run the assumption check before requirements, system designs, or implementation plans. Reuse settled answers throughout the design package. An assumption check does not require an interview when the material choices are already clear. For a standalone interview or stress test, clarify intent without automatically creating a design package. Skip this workflow for mechanical edits and pure information requests. ## 1. Check assumptions Read the request, relevant specifications, source, and tests. Separate: - **Confirmed:** the user explicitly requested or previously settled it. - **Verified:** source, tests, or documentation establish a fact. Keep its source reference and distinguish current behavior from intended behavior. - **Unresolved:** a choice or missing fact can change behavior, scope, ownership, permissions, persistence, compatibility, or acceptance criteria. State the intended outcome and material unresolved assumptions briefly. Do not invent confidence percentages. Investigate facts that available tools can resolve before asking the user. Evidence of current behavior is not user agreement to preserve it. Ask about consequential choices that evidence cannot settle. Choose routine, reversible implementation details within the agreed scope. A request for speed reduces questions; it does not make an unanswered material choice confirmed. For a clear regression, use the active acceptance criterion without asking the user to define the behavior aga...