wayfinder

Invoke the skill with your loose idea to chart a map: it names the destination through a grilling session, creates a map issue labeled wayfinder:map, and files the specifiable decisions as child tickets. Each later session resolves exactly one ticket until the route is clear.

The skill runs a breadth-first grilling pass to surface open decisions, then creates tickets only for questions that are already sharp. Everything still fuzzy is recorded in the map's Not yet specified section and graduates into tickets as the frontier advances.

The map, tickets, blocking, and frontier queries are tracker-specific and defined in docs/agents/issue-tracker.md for each repo. If that document is absent, the skill defaults to a local-markdown tracker instead of a hosted one.

Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed items. The frontier is the set of open, unblocked, unassigned child tickets, and blocking uses the tracker's native dependency relationship.

Skip the map when charting surfaces no fog, meaning the way to the destination is already clear and the whole effort fits in one session. The skill also avoids execution: it produces decisions, not deliverables, unless an effort's Notes explicitly override that default.