wayfinderlisted

# Wayfinder An idea has arrived that is too big for one session and wrapped in fog: the way from here to the **destination** isn't visible yet. Wayfinding finds that way — it does not charge at the destination. This skill charts the way as a **map** under `docs/plans/`, then works its **decision tickets** — questions whose resolution is a decision, not slices of a build to execute — one per session until the route is clear. ## When to use - A greenfield project or a large feature build where you can feel the shape of the work but cannot yet write it as a spec. - More than one 100K-token session of thinking stands between here and a plan. **Skip when** the effort fits one session — grill it and write the spec directly. Skip when the plan already exists and only needs slicing; that is `plan-audit` territory, not wayfinding. This is the heaviest planning flow here: reaching for it on a well-scoped feature costs several sessions and buys nothing. ## Plan, don't do Every ticket resolves a decision, and the map is done when nothing is left to decide before someone goes and builds the thing. The pull to just do the work is the signal you have reached the edge of the map — that is the moment to hand off to a spec, not to start implementing. An effort can override this in the map's **Notes**; absent that, produce decisions, not deliverables. ## The map The map is `docs/plans/<effort-slug>/map.md`, its tickets are `docs/plans/<effort-slug>/tickets/NN-<slug>.md`, numbered from `