Interview Me (Interactive Requirements & Design Alignment)

Thoroughly interview the user about every aspect of their task until reaching a complete, shared technical and product understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.

Rules

1. Codebase First (Silent Exploration):
   • Before asking any question, actively explore existing code, schema definitions, protobuf contracts, config files, and documentation.
   • Never ask the user questions that can be answered by reading the codebase.
2. One Question at a Time:
   • Never overwhelm the user with long lists of questions.
   • Focus exclusively on the single most critical blocking decision point in each turn.
3. Bring Recommendations:
   • For every question, always provide a clear recommended option (marked with (Recommended)) and explain the trade-offs concisely.
4. Native Interactive Tool First:
   • Prefer calling the runtime's native interactive prompt/selection tool (AskFollowupQuestion in Claude Code, ask_question in Antigravity, etc.).
   • Fall back to clean Markdown numbered choices only when running in a bare CLI environment without interactive tool capabilities.
5. Top-Down Decision Tree:
   • Resolve decisions in order: System Boundaries -> Architecture & Data Flow -> Storage & Schema -> API Contracts -> Edge Cases.