Wayfinder Plus

A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the destination isn't visible yet. Wayfinding finds that way instead of charging at the destination. Chart the way as a shared map on the project's issue tracker, then work its tickets one at a time until the route is clear.

Naming the destination is the first act of charting — it shapes every ticket. It might be a spec to hand to to-spec-plus, a decision to lock before planning starts, or a change made in place (a data-model migration, an expand–contract schema change).

Pipeline position: wayfinder-plus (find the way) → to-spec-plus (write the spec) → to-tickets-plus (slice it) → implement-plus (build one slice per session).

Plan, don't do

Each ticket resolves a decision; the map is done when nothing is left to decide before someone goes and does the thing. The pull to just do the work is usually the signal you've reached the edge of the map and it's time to hand off. An effort can override this in its Notes — carrying execution into the map itself — but absent that, produce decisions, not deliverables.

Refer by name

Every map and ticket is an issue, so it has a name — its title. In everything the human reads, refer to it by that name with the id/URL riding inside as a link — never a bare #42 or LIN-42. A wall of ids is illegible; names read at a glance.

The Map

The map is a single issue labelled wayfinder:map — the canonical artifact. Its tickets are child issues of the map.