Plan Interview

A relentless, interactive interview pattern. One question at a time. Each question resolves a single decision in the plan or design tree. Each question ships with a recommended answer and rationale. Anything answerable from the codebase is answered by reading the code, not by asking. The loop ends when no open branches remain.

When to use

• The user pasted a plan, design doc, RFC, or PR description and wants it stress-tested before implementation.
• The user said "grill me", "interview me", "walk me through this", "what am I missing", "find the gaps in this plan".
• You are about to implement something non-trivial and the spec has obvious unresolved branches (auth model, error semantics, rollout strategy, etc.).
• The user explicitly asked for shared-understanding alignment before code is written.

Skip this skill for: trivial work where the answer is obvious, batch self-interrogation (use deep-discovery for that), or pure code review of an existing diff (use qa or a code-review pattern instead).

How this is different from deep-discovery

• deep-discovery is a self-dialogue: you ask 100 questions internally and produce a synthesis. The user sees only the result.
• plan-interview is interactive: you ask the user one question, wait for their answer, then ask the next. The user sees every question.

If the user wants a final stress-test report without round-trips, route to deep-discovery. If they want to think through the plan with you, stay here.