Interview

Conduct a detailed interview to gather requirements and produce a written specification. The interview starts broad (problem discovery) and progressively converges toward a concrete implementation plan.

$ARGUMENTS

Critical Rules

ALWAYS:

• Explore the codebase BEFORE asking questions — understand existing patterns, models, and domain concepts first
• Use AskUserQuestion for every interview question — never assume answers
• Ask ONE focused question at a time (with 2-4 options when appropriate) — avoid walls of questions
• Write the final plan to a file, not just chat output
• Write the plan in the same language the user uses

NEVER:

• Skip Phase 1 (context gathering) — uninformed questions waste the user's time
• Ask more than 2 questions per turn
• Continue interviewing when you have enough information — converge and write the plan