interview-planlisted

# Plan Interview Produce **one ambiguity-free implementation plan** by interviewing the user **one question at a time**. The crucial goal is a plan with **no ambiguity** across three lenses: - **Business requirements** — what problem, measurable success, who, why not simpler. - **Backward compatibility** — every consumer, stored record, in-flight message, and deployed client affected, **enumerated from the actual code**. - **Technical** — behaviour, edge cases, data model, contracts, testing, rollout. The model **discovers and interrogates** — it reads the codebase first, confronts the user with findings, and pushes back with alternatives. It does **not** prepare a plan from the user's words alone. A plan built only from what the user said is the failure mode this skill exists to prevent. The single output is **one plan markdown file written to disk** — authored by the **write-plan** skill from the spec this interview assembles, then verified by this skill's Audit Pass. It must be complete enough that a fresh reader can implement it without a follow-up question. The goal is not "minimum questions to start coding". It is "no ambiguity left that would bite us at code-review or in production". ## Rules 1. **One question per turn.** Never bundle multiple questions, sub-questions, or "while we're at it" asides. If you catch yourself writing "and also" — delete it and save it for the next turn. (Batch-confirmations of clearly out-of-scope checklist items are n