Plans large multi-session efforts as issue-tracker maps of investigation tickets.
npx skills add https://github.com/titaneric/dotfiles --skill wayfinder-titaneric
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/titaneric/dotfiles/tree/main/dot_agents/skills/wayfinder Command: npx skills add https://github.com/titaneric/dotfiles --skill wayfinder-titaneric
wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope boundaries, with child issues as tickets. - Typed tickets with blocking: Each ticket is typed as research, prototype, grilling, or task, claimed by assignment, and ordered via the tracker's native blocking relationships so the actionable frontier is visible. - Incremental resolution: Sessions claim one frontier ticket, resolve it through grilling, prototyping, or research, record the answer as a resolution comment, and graduate newly specifiable fog into fresh tickets. - Use Case: A team needs to plan a data-structure migration too big for one session. Wayfinder charts a map naming the migration as the destination, tickets the sharp open questions, parks vague concerns in Not yet specified, and works tickets one per session until every decision is made. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your loosely defined project idea, or invoke it with an existing map issue URL to work the next open ticket.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, creates a map issue on the tracker, tickets the sharp open questions, and parks vague areas in Not yet specified. Later sessions work one ticket at a time until the way is clear.
Wayfinder runs a breadth-first grilling session to surface open decisions, then creates child issues typed as research, prototype, grilling, or task. Blocking edges are wired in a second pass so the tracker shows which tickets are actionable.
Wayfinder is tracker-agnostic: it consults the tracker doc's Wayfinding operations section for how the repo expresses maps, child tickets, and blocking. If no tracker is provided, it defaults to a local-markdown tracker.
No. Wayfinder strictly resolves at most one ticket per session, claiming it by assignment before work begins. This lets multiple sessions run unblocked frontier tickets in parallel without conflicts.
Skip wayfinder 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 plans rather than executes by default, producing decisions, not deliverables.
The-Focus-AIPlan large efforts as decision-ticket maps on an issue tracker.
nesquikmCoordinate structured design sessions to explore open-feature ideas.
pd-phucConverts loose ideas into sequenced investigation tickets tracked in a git-managed markdown decision map.
NAMEWTAPlans large ambiguous work as a map of investigation tickets on an issue tracker.