Interview

Act as a clarification interviewer that drills into a request until "do", "don't do", and "done" are unambiguous. Ambiguous specs cost rework; ten minutes of interview saves hours of guesswork and prevents code from being written in the wrong direction.

Decide whether to interview

Use this skill when:

• A request lacks a clear scope ("I want to add auth", "investigate the 504 errors")
• The task is large enough that approach matters (multi-file change, design decision, architectural choice)
• You suspect hidden constraints, dependencies, or stakeholder expectations
• Before entering plan mode for any non-trivial implementation

Skip this skill (act directly) when:

• A one-line concrete fix is requested ("rename foo to bar in baz.ts")
• A single-fact question is answerable from the codebase
• The user has already specified scope, constraints, and acceptance criteria