Use an Interview to Expose Gaps in the Brief

The stakeholder asks for a useful assistant. Before choosing a framework, find out which result they would accept and which mistake they cannot tolerate.

Ask Claude to interview you about the task: inputs, users, edge cases, permissions, failure handling and trade-offs. Have it record answered questions and unresolved assumptions in SPEC.md.

The interview can expose a question you missed. It cannot answer on the stakeholder's behalf or turn a plausible assumption into an approved requirement. Review the proposed scope with the people who own the data and outcome.

Then give the implementation session the agreed brief, acceptance examples and unresolved decisions. A fresh conversation can reduce irrelevant history; the important handoff is the verified specification. Start building when you can explain what success means and who will judge it.