flashlight
A wayfinder map charts a large effort as decision tickets on the issue tracker, wrapped in fog. Its frontier — the open, unblocked, unclaimed tickets — advances in its own order.
A flashlight is the human's beam. They point it at one direction, and this session walks in now, out of frontier order, to learn what lies that way.
/flashlight <map> <request>. Ask for the map when the invocation omits it. Shine one beam per session.
Where the map, its child tickets, blocking edges, claims and the frontier query physically live is tracker-specific. Consult the tracker doc's "Wayfinding operations" section for how this repo expresses each one. Default to the local-markdown tracker when no tracker doc is present.
Two beams
Read <request>, and ask one question: is the subject the map, or the territory?
- Territory — the work itself. "Can we use SQLite for the queue?" → Shine into the territory.
- Map — the chart you already drew: what to focus on, what to defer, what no longer belongs. "We have too many open tickets — what should we focus on?" → Redraw the map.
Ask the human to choose when the request reads both ways.