Interview Me

Move from ambiguity to clarity before building. Read the codebase, then Socratically interview the user — surfacing hidden assumptions and testing their framing — until you could confidently hand this off to be built.

When to use

When the task is non-trivial and the goal is vague, has multiple valid interpretations, or touches unfamiliar areas.

When NOT to use

• User has a specific request with file paths, function names, or exact behavior
• Quick fix, typo, or single obvious change
• User says "just do it" or "skip the questions"
• User already has a PRD or detailed spec

Protocol

1 — Read context first