visionlisted

# Vision — Keep What the Building Is For On File Devour knows the city, isomorph finds its twin, bedrock proves it stands, potential sees what it becomes — and all of them open by asking the same question: *what is this building trying to be?* Bedrock needs it so "light" never means lobotomized. Potential needs it because the vision is the client. Any implementing agent needs it so it builds toward the experience instead of around it. This skill keeps the answer written down and alive: one artifact, `VISION.md`, at the repo root. Ideas are *born* elsewhere — in an exploration room like warroom, in riffing conversation — and the intent at birth is vivid. Then months of building happen, the intent evolves in chats and taste calls, and the file (if it exists at all) still says what was believed on day one. A vision document that no longer matches the visionary is worse than none: every skill that reads it inherits a false north star. ## The Constitutional Rule **The vision comes from the visionary.** Code can show what was built — never what it is *for*. The skill may draft from evidence (the repo, MAP.md, old notes, exploration trails), but the user's voice confirms, corrects, and decides. Never fabricate intent. What the user has not said belongs in Open Questions, not in invented prose. And its corollary, inherited from how the user actually works: **the spark stays verbatim, and the user's wording is the specification.** Rough phrasing that carries the real instinct bea