interviewlisted

# /interview [feature or task] Structured requirements discovery through interactive questioning. ## Usage ``` /interview user authentication feature /interview redesign the task board UI /interview # ask about the current task ``` ## Interview Process ### Phase 1: Context (1-2 questions) Understand the starting point: - What exists today? What are the pain points? - Who is the user? What's the expected load/scale? ### Phase 2: Core Requirements (2-3 questions) Pin down must-haves: - What does "done" look like? What's the primary success metric? - What are the hard constraints? (performance, compatibility, deadlines) - What integrates with this? What must NOT break? ### Phase 3: Edge Cases & UX (1-2 questions) Surface the tricky parts: - What happens when X fails / is empty / is at max? - Any accessibility, i18n, or mobile requirements? ### Phase 4: Technical Preferences (1-2 questions, if unclear) Resolve approach ambiguity: - Any technology constraints? (must use X, can't use Y) - Existing patterns to follow? (point to similar code) ## Rules - **Max 4 questions per AskUserQuestion call** — don't overwhelm - **Never repeat** a question that was answered - **Stop** when you have enough to write an unambiguous spec - Typical interview: 3-6 questions total across 2 rounds ## Output: SPEC.md After the interview, write the spec to `SPEC.md` (or a path the user specifies): ```markdown # Spec: [Feature Name] ## Goal One sentence: what