keel-wayfindlisted

# keel-wayfind — Decision Maps for Oversized Work ``` INPUT an idea too large for one session whose route is still unclear — fog, not just size OUTPUT docs/maps/<topic>/MAP.md with zero open tickets and no fogged section, exiting to keel-discover or keel-plan ``` Missing INPUT → `BLOCKED: 缺 <foggy oversized idea> → 退回 the requester`. In practice the miss is the other way round: this is the wrong stage. Work that is merely large but whose route is visible goes straight to `keel-discover`; the fog is the entry condition, not the size. A loose idea has arrived — too big for one session, and wrapped in fog: the route from here to the **destination** isn't visible yet. Wayfinding charts that route as a map of **decision tickets** — questions whose resolution is a decision, not slices of a build — and resolves them one at a time. **Plan, don't do.** Every ticket resolves a decision. The map is done when nothing is left to decide — then the effort exits to **keel-discover** (spec the now-clear work) or **keel-plan** (if the decisions already amount to a spec). Feeling the pull to just start building is the signal you've reached the map's edge and it's time to exit, not to code inside the map. **When NOT to use:** if one keel-discover session could plausibly settle all open questions, skip the map — this skill's overhead only pays off when the deciding itself spans sessions. ## File layout ``` docs/maps/<topic>/ ├── MAP.md ← the map: low