wayfinderlisted

# Wayfinder Use Wayfinder when an effort is too large and uncertain for one session. It charts a shared map on the configured issue tracker and resolves decision tickets until the route to a buildable specification is clear. Before starting, verify the model-invoked companions `/grilling`, `/domain-modeling`, `/research`, `/prototype`, and `/delivery-proof` are installed. Name missing dependencies and do not pretend their decision or proof gate ran. ## Plan, do not silently build Wayfinder produces decisions and delivery obligations, not implementation. A `task` ticket may perform work needed to obtain decision evidence, but it does not deliver the product outcome. Execution begins through `/to-spec`, `/to-tickets`, and `/implement` unless the user explicitly defines a different planning destination. Never resolve more than one non-research ticket per session. Refer to every map and ticket by its linked title, not a bare identifier. ## Two destinations - **Desired outcome** — the real user or business result that must eventually be true. It does not become true merely because planning is complete. - **Planning destination** — the artifact Wayfinder will make ready, normally a specification handoff. Every scope decision must preserve the desired outcome. An item may be out of this map only if the desired outcome remains true without it, or if it is carried forward as an owned obligation. ## The map The map is the tracker-native map artifact; its decision tickets are