Plans large efforts as decision-ticket maps on an issue tracker.
npx skills add https://github.com/AlexanderNarbaev/agi --skill wayfinder-alexandernarbaev
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/AlexanderNarbaev/agi/tree/main/.opencode/skills/matt-pocock/wayfinder Command: npx skills add https://github.com/AlexanderNarbaev/agi --skill wayfinder-alexandernarbaev
wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope boundaries. - Typed decision tickets: Splits work into research, prototype, grilling, and task tickets, each sized to one agent 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: A team facing a vague data-migration effort invokes Wayfinder to name the destination, fan out the open decisions into tickets, fire parallel research subagents, and then resolve tickets session by session until the spec is fully decided. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your loosely defined initiative, naming the destination and the first decision tickets on your issue tracker.High-intent search queries and answers about installing and using this skill.
Invoke Wayfinder with your loose idea to chart a map: it names the destination, fans out open decisions breadth-first, and creates decision tickets as child issues on your issue tracker. Each ticket is then resolved one per session until the route is clear.
A decision ticket is a child issue of the map whose resolution is a decision rather than 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 the tracker to support labels, child issues, assignment, and ideally native blocking relationships. If no tracker is provided, it defaults to a local-markdown tracker and asks you to run the setup command.
Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. Unblocked frontier tickets can be resolved in parallel, with research tickets resolved by subagents.
Skip it when charting surfaces no fog — if the way to the destination is already clear and the whole journey fits one session, no map is needed. It also produces decisions, not deliverables, unless an effort explicitly overrides this in its Notes.
The-Focus-AIPlan large efforts as decision-ticket maps on an issue tracker.
anionzoConvert vague requests into concrete directions with locked decisions.
mst-software-vnConverts loose ideas into sequenced investigation tickets tracked in a markdown decision map.
EpicenterHQPlans multi-session work as decision tickets tracked on a repository issue tracker.