wayfinder

Invoke wayfinder with your loose idea to chart a map: it names the destination, sketches unspecifiable questions into a fog-of-war section, and creates decision tickets as child issues on your issue tracker. Each ticket is then resolved one per session until the route is clear.

A decision ticket is a child issue of the map whose resolution is a decision rather than a build deliverable. Each carries a type label — research, prototype, grilling, or task — and is sized to fit one 100K-token agent session.

Wayfinder is tracker-agnostic but expects the tracker to support labels, child issues, assignment, and native blocking relationships. If no tracker is provided, it defaults to a local-markdown tracker, and tracker-specific operations are documented per repo.

Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. The frontier — open, unblocked, unclaimed tickets — is what parallel sessions draw from.

Skip wayfinder when the path to the destination is already clear and the whole effort fits in one session — charting surfaces no fog in that case. It is also planning-oriented by default, so pure execution work belongs elsewhere unless the map's Notes opt into execution.