Plans large multi-session efforts as decision tickets on an issue tracker.
npx skills add https://github.com/sanjanb/my-agent-harness --skill wayfinder-sanjanb
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/mp-wayfinder Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill wayfinder-sanjanb
wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope sections. - Typed decision tickets: Breaks work into research, prototype, grilling, and task tickets, each sized to one 100K-token session, with native blocking relationships defining the frontier. - Two invocation modes: Chart a new map from a loose idea, or work through an existing map by claiming and resolving one ticket per session. - Use Case: You have a vague migration idea too big for one session. Invoke wayfinder to grill out the destination, create the map and initial tickets, fire research subagents, then resolve tickets session by session until the route is clear. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your large idea, naming the destination and creating the first decision tickets on the issue tracker.High-intent search queries and answers about installing and using this skill.
Use wayfinding: chart a map issue on the repo's issue tracker that names the destination, then create decision tickets as child issues. Resolve one ticket per session until no decisions remain and the way to the destination is clear.
A decision ticket is a child issue of the map whose resolution is a decision, not a build slice. Each carries a type label — research, prototype, grilling, or task — and is sized to fit one 100K-token agent session.
Wayfinder is tracker-agnostic but expects labels, child issues, assignees, and native blocking relationships. The tracker doc's Wayfinding operations section defines how a given repo expresses these; without one it defaults to a local-markdown tracker.
Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. The frontier — open, unblocked, unclaimed tickets — is what parallel sessions draw from.
Skip it when the way to the destination is already clear and the whole journey fits one session — charting surfaces no fog in that case. It is also planning by default, so it produces decisions, not deliverables, unless the map's Notes override this.
The-Focus-AIPlan large efforts as decision-ticket maps on an issue tracker.
CoreStack-EnggSynchronize project state, sprint context, and ADRs across agent teams.
pd-phucConverts loose ideas into sequenced investigation tickets tracked in a git-managed markdown decision map.
joshmandersConvert planning conversations into tracked GitHub issues mapped to a single PR.