Wayfinder

Use this for a loose idea that is too large for one agent session and whose route is still unclear. Wayfinding names the destination, charts a map on the repo's issue tracker, and works its decision tickets — questions whose resolution is a decision, not slices of a build to execute — until the route is clear.

This is a situational on-ramp to the tracer flow, not its default entry. A feature whose decisions fit in one session belongs in /tracer-interview-me instead.

Plan, don't do

Wayfinder plans. Its destination is a spec-ready set of decisions, and each decision ticket ends in an answer. The map is complete when nothing remains to decide before someone builds the work.

The urge to start building means you have reached the destination. Hand the cleared map to /tracer-to-spec; never send a multi-session map directly to /tracer-implement, which would skip the step that collapses its distributed detail.

Refer by name

Every map and ticket has a title. In narration and in Decisions so far, refer to an issue by its linked name, never by a bare id, number, path, or slug. Identifiers still appear inside links; they do not stand in for names.

The map

The map is one issue labelled wayfinder:map, or the local equivalent documented by the tracker. Its decision tickets are children of that map.