wayfinder

Invoke the skill with your loose idea to chart a map: it names the destination, creates a tracker issue labelled wayfinder:map, and files each open decision as a child ticket. Later sessions work through one ticket at a time until the route is clear.

The skill grills you breadth-first to surface open decisions, then creates child issues for questions that are already sharp and parks the rest in a Not yet specified fog section. Each ticket gets a type label: research, prototype, grilling, or task.

Yes, the map, tickets, blocking, and frontier queries are tracker-specific and follow the tracker doc's Wayfinding operations section. If no tracker is provided, it defaults to a local-markdown tracker.

Yes, sessions claim tickets by assigning them before starting work, so concurrent sessions skip claimed items. The frontier is the set of open, unblocked, unclaimed child tickets, and blocking uses the tracker's native dependency relationship.

Skip it when the way to the destination is already clear and the whole journey fits in one session; the charting step explicitly stops and asks how to proceed in that case. It also produces decisions, not deliverables, unless an effort's Notes override that default.