Turning a Vague Feature Idea Into a Spec Before Coding
You want Claude Code to interview you about a large new feature — asking about implementation, UI/UX, edge cases, and tradeoffs — before anything gets built.
What should the resulting workflow look like, per this subject?
The correct answer is "Interview you into a SPEC.md, then execute in a fresh session."
Claude interviews you (using the AskUserQuestion tool) until the
decisions are covered, writes a complete spec to SPEC.md, and then
a fresh session executes it — clean context for implementation, and
a written artefact to review the result against. Implementing in the
same session that ran the interview keeps all that back-and-forth in
context unnecessarily; writing the spec yourself first defeats the
point of the interview; and the interview doesn't replace plan mode —
it feeds into the plan, it doesn't skip it.
Share this question