Plan large efforts as decision tickets on an issue tracker and resolve them one at a time.
npx skills add https://github.com/GregM1991/skills --skill wayfinder-gregm1991
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/GregM1991/skills/tree/main/skills/vendor/mattpocock/wayfinder Command: npx skills add https://github.com/GregM1991/skills --skill wayfinder-gregm1991
wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope boundaries. - Typed decision tickets: Each child ticket is one of research, prototype, grilling, or task, with HITL or AFK modes, native blocking relationships, and claim-by-assignment for concurrent sessions. - Progressive resolution: Sessions claim one frontier ticket at a time, record resolutions as comments, and graduate newly specifiable fog into fresh tickets until the way is clear. - Use Case: You have a vague migration idea too big for one session. Invoke charting to name the destination, fan out the open decisions into tickets, fire research subagents in parallel, then work through the frontier ticket by ticket across multiple sessions. ## Quick Start Ask the agent to chart a wayfinder 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.
Invoke the charting mode with your loose idea. The skill names the destination, grills breadth-first to surface open decisions, creates a map issue labelled wayfinder:map, and files the specifiable questions as child tickets with blocking edges.
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), is sized to one agent session, and is claimed by assignment before work begins.
It works with whatever issue tracker the repo provides, consulting that tracker's documentation for how maps, child tickets, and blocking are expressed. If no tracker is provided, it defaults to a local-markdown tracker.
Yes. Sessions claim tickets by assigning themselves before starting, so concurrent sessions skip claimed work. The frontier is the set of open, unblocked, unclaimed tickets, and each session resolves at most one ticket, except research tickets.
Skip the map when charting surfaces no fog, meaning the way to the destination is already clear and the whole journey fits in one session. In that case the skill stops and asks how you would like to proceed instead.
Ab0umarPlans large efforts as decision tickets on an issue tracker.
anionzoConvert vague requests into concrete directions with locked decisions.
Fatih0234Plans large efforts as decision tickets on an issue tracker and resolves them one at a time.
AO-HySPlans large efforts as decision-ticket maps on an issue tracker.