Plans large multi-session efforts as decision-ticket maps on an issue tracker.
npx skills add https://github.com/yamcodes/the-hat --skill wayfinder-yamcodes
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/yamcodes/the-hat/tree/main/skills/wayfinder Command: npx skills add https://github.com/yamcodes/the-hat --skill wayfinder-yamcodes
wayfinder:map) holding the destination, notes, decisions-so-far, fog of war, and out-of-scope sections, with tickets as child issues. - Typed Decision Tickets: Classifies tickets as research (AFK), prototype (HITL), grilling (HITL), or task, each sized to one agent session and claimed via assignment to prevent concurrent-session conflicts. - Frontier Tracking: Uses the tracker's native blocking relationships so open, unblocked, unclaimed tickets form a visible frontier; resolving a ticket graduates fog into new tickets. - Use Case: A team faces a vague data-structure migration too big for one session. Wayfinder names the destination, fans out the open decisions breadth-first, creates research and grilling tickets, and works them one per session until the migration plan is fully decided. ## Quick Start Ask your AI assistant to chart a wayfinder map for a loosely defined effort, naming the destination and the first decisions to resolve.High-intent search queries and answers about installing and using this skill.
Chart a wayfinder map: name the destination, fan out the open decisions breadth-first, and create child-issue tickets on the issue tracker. Then work through the frontier one ticket per session until no decisions remain.
A decision ticket is a child issue 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 needs child issues, labels, assignment, and ideally native blocking relationships. The tracker-specific operations live in a tracker doc; if none is provided, it defaults to a local-markdown tracker.
A session claims a ticket by assigning it to the dev driving the map before any work begins. An open, unassigned ticket is unclaimed, so concurrent sessions skip assigned tickets automatically.
Skip the map when breadth-first grilling surfaces no fog, meaning the way to the destination is already clear and the whole journey fits in one session. In that case, stop and ask the user how to proceed directly.
Fog of war is in-scope work toward the destination that cannot yet be phrased as a sharp ticket; it graduates into tickets as the frontier advances. Out of scope is work ruled beyond the destination and never graduates.
AnasIsmai1Decomposes vague ideas into tracked investigation tickets on an issue tracker.
QT-7274Plan large efforts as decision tickets on an issue tracker and resolve them incrementally.
mst-software-vnConverts loose ideas into sequenced investigation tickets tracked in a markdown decision map.
foomakersRecord technical decisions as ADRs or ADLs and update adoption files.