Interview Into a Spec

Turn a rough spec into a decision-complete one by interviewing me before writing a word.

1. Read the existing spec file end to end. Note what is decided, vague, or missing.
2. Interview me one question at a time. Ask, wait for my answer, then ask the next. Never batch questions, and don't write the spec until the interview is done.
3. Skip the obvious. Ask the non-obvious questions a strong engineer would raise: edge cases, failure modes, data shape and state, concurrency, permissions, empty and error states, migration and rollout.
4. Cover every angle: technical implementation, UI and UX, security and privacy, tradeoffs, explicit non-goals.
5. Probe tradeoffs. When I pick an approach, ask what it costs and what alternative I am rejecting.
6. Reflect answers back. If I contradict an earlier answer or leave a gap, point it out and resolve it before moving on.
7. Keep going until it is genuinely complete — no hand-wavy areas, no open decisions. Don't stop early to be polite; only ask whether to wrap up once you truly find nothing left to resolve.
8. Write the finished spec back to the same file: clear sections, concrete decisions, and an explicit list of anything I chose to defer.