Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a…
A loose idea has arrived — too big for one agent session, and wrapped in fog: the route from here to a plan isn't visible yet. This skill charts it as a shared map on the repo's issue tracker, then works its tickets one at a time. The map is domain-agnostic — engineering work, course content, whatever fits the shape. Refer by name Every map and ticket is an issue, so it has a name — its title. In everything the human reads — narration, the map's Decisions-so-far — refer to it by that name, never by a bare id, number, or slug. A wall of #42, #43, #44 is illegible; names read at a glance. The id and URL don't vanish — a name wraps its link — but they ride inside the name, never stand in for it. The Map The map is a single issue on this repo's issue tracker, labelled wayfinder:map — the canonical artifact. Its tickets are child issues of the map. The map is an index, not a store. It lists the decisions made and points at the tickets that hold their detail; a decision lives in exactly one place — its ticket — so the map never restates it, only gists it and links. Where the map, its child tickets, blocking, and frontier queries physically live is tracker-specific. Consult docs/agents/issue-tracker.md (the "Wayfinding operations" section) for how this repo expresses them. If that doc is absent, default to the local-markdown tracker. The map body The whole map at low resolution, loaded once per session. Open tickets are not listed — they are open child issues, found by query.
don't have the plugin yet? install it then click "run inline in claude" again.