Plan large multi-session efforts as decision tickets on an issue tracker.
npx skills add https://github.com/peachest/skills --skill wayfinder-peachest
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/peachest/skills/tree/main/in-progress/wayfinder Command: npx skills add https://github.com/peachest/skills --skill wayfinder-peachest
wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope sections, with child issues as decision tickets. - Typed tickets with frontier tracking: Classifies tickets as research, prototype, grilling, or task (HITL or AFK), uses native tracker blocking to compute the frontier of takeable work, and claims tickets by assignment to avoid concurrent-session conflicts. - Discovery routing: Routes mid-effort findings through four ordered branches — external ownership, sub-ticket, new map, or not-yet-gradeable — with human confirmation before anything is created. - Use Case: You need to plan a data-structure migration too big for one session. Invoke the Skill to grill out the destination, create a map issue with the first decision tickets wired by blocking edges, then resolve one ticket per session until the way is clear. ## Quick Start Ask the agent to chart a map for your loosely defined effort, for example: use wayfinder to plan the authentication redesign as decision tickets on our issue tracker.High-intent search queries and answers about installing and using this skill.
Chart it as a map issue on the repo's issue tracker with child decision tickets. Each ticket is sized to one 100K token session, and sessions resolve one ticket at a time until no decisions remain before execution.
A decision ticket is a child issue whose resolution is a decision rather than a build slice. It carries a type label — research, prototype, grilling, or task — and its answer is recorded as a resolution comment when closed.
Yes, the map and tickets live on whatever issue tracker the repo uses, with tracker-specific operations documented per tracker. If no tracker is provided, it defaults to a local-markdown tracker managed by a tracker CLI.
Blocking uses the tracker's native dependency relationship so the frontier renders visually in the tracker UI. A ticket is unblocked when everything blocking it is closed; the frontier is the open, unblocked, unclaimed children.
When the finding changes premises of open tickets or sits at a different altitude than the current destination. The agent proposes the branch and the human confirms before a new map is chartered.
Yes, sessions claim tickets by assigning them before starting work, so concurrent sessions skip claimed tickets. Research tickets are the exception to the one-ticket-per-session rule and can run in parallel as subagents.
fallguyconsultingBootstraps a design corpus by discovering concepts, stories, and decisions from a codebase.
IsKenKenYaPlans large efforts as decision-ticket maps on an issue tracker.
PVMaloveRuns a structured interview session to sharpen a plan or design.
NAMEWTAPlans large ambiguous work as a map of investigation tickets on an issue tracker.