wayfinder

Plan large multi-session efforts as issue-tracker maps of investigation tickets.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill wayfinder-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/2026-09-10/wayfinder
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill wayfinder-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, fuzzy initiatives often exceed what a single agent session can hold, leaving decisions scattered and progress untracked. Wayfinder turns a loose idea into a shared map of investigation tickets on your issue tracker, then resolves them one at a time until the path to the destination is clear. ## Core Features & Use Cases - Map-based planning: Creates a single map issue (labelled wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope sections. - Typed tickets: Each child ticket is tagged as research, prototype, grilling, or task, and is claimed, blocked, and resolved through the tracker's native features. - Frontier workflow: Sessions pick the next unblocked, unclaimed ticket, resolve exactly one per session, and graduate newly clarified fog into fresh tickets. - Use Case: You need to plan a data-structure migration too big for one session. Wayfinder charts a map of research and decision tickets on your issue tracker, and each subsequent session works one ticket until the route is fully decided. ## Quick Start Ask the agent to chart a wayfinder map for your loosely defined initiative, naming the destination and the issue tracker to use.

Frequently Asked Questions about wayfinder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a project too big for one agent session?

Chart a wayfinder map: name the destination, run a breadth-first grilling to surface open decisions, then create a map issue with child tickets for each sharp question. Each later session resolves exactly one ticket until the way is clear.

How do I track investigation tickets on an issue tracker?

Create a single map issue labelled wayfinder:map and make each investigation a child issue with a wayfinder type label (research, prototype, grilling, or task). Use the tracker's native blocking relationships so the frontier of takeable tickets renders visually.

What issue trackers work with wayfinder maps?

Wayfinder is tracker-agnostic and consults the tracker doc's Wayfinding operations section for how a given repo expresses maps, child tickets, and blocking. If no tracker is provided, it defaults to a local-markdown tracker.

When should I not use a wayfinder map?

Skip the map when breadth-first exploration surfaces no fog, meaning the whole journey fits in one session. Also avoid it for pure execution work, since wayfinder produces decisions, not deliverables, unless the effort's Notes override this.

Why limit each session to resolving one ticket?

Each ticket is sized to one 100K token agent session, and resolving more than one risks shallow answers and lost context. The one-ticket rule also keeps claiming, blocking, and concurrent parallel sessions consistent on the tracker.