to-visionlisted

# to-vision Run an adaptive interview that turns a founder's raw idea into a seven-field vision artifact, gate it through a sharpness check, and record it only once the founder explicitly approves. ## Before starting Check whether `docs/product/vision.md` already exists in the founder's repo. - **If it doesn't exist**, this is a from-scratch session. Proceed with the interview below. - **If it exists**, read it and tell the founder a vision is already recorded there, showing them its current fields. Continue with the interview below, using the existing content as the starting point for each field's answer (read it back to the founder and let them confirm or revise it, rather than asking cold). Check the frontmatter for `approved_by`/`approved_at` first, since that changes what an edit here means, then follow whichever of these two applies: - **Drafted** (no `approved_by`/`approved_at` present) — an ordinary continuation of an unfinished draft. `update` the file in place, rather than treating this as a second `create`, once the founder approves (see Approval and Writing the artifact). - **Approved** (`approved_by`/`approved_at` present) — any field edit the founder lands here is a *revision* to an already-approved artifact. As soon as an edited field is confirmed, `update` `docs/product/vision.md` in place with the change — same mechanism, no parallel version history — and in that same write add a dated revision-reason marker to the frontmatter (see Writing the artifac