Plan large efforts as decision tickets on a GitHub issue tracker.
npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill wayfinder-benjr70
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/benjr70/Smart-Smoker-V2/tree/main/.claude/skills/wayfinder Command: npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill wayfinder-benjr70
wayfinder:map) holding the destination, notes, decisions-so-far index, fog-of-war items, and out-of-scope rulings, with child issues as decision tickets. - Typed ticket routing: Classifies tickets as research, prototype, grilling, or task, each labelled AFK or HITL, with GitHub Project membership and Priority fields driving automated pickup by a Daemon. - Frontier management: Uses native GitHub blocking relationships so open, unblocked, unclaimed tickets form a visible frontier; sessions claim, resolve, and close one ticket at a time. - Use Case: A team facing a vague migration goal invokes the Skill to grill out the destination, fan out open questions into labelled child issues, fire research subagents in parallel, and then work through the frontier session by session until every decision is recorded. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your large, loosely-defined effort, or point it at an existing map issue URL to work through the next decision ticket.High-intent search queries and answers about installing and using this skill.
Invoke the wayfinder skill with your loose idea. It grills you to name the destination, maps open questions breadth-first, creates a map issue plus labelled child tickets on GitHub, and wires blocking edges so each future session resolves one ticket at a time.
The skill creates a map issue labelled wayfinder:map and child tickets typed as research, prototype, grilling, or task. Each ticket is sized to one agent session, labelled AFK or HITL, and connected with native GitHub blocking relationships.
AFK tickets (research and human-free tasks) are driven by the agent alone and added to Project #1 with a Priority for automated pickup. HITL tickets (grilling, prototype, human-needed tasks) require live human exchange and are never added to the project.
The map-and-ticket model is tracker-agnostic, but this fork's concrete operations (labels, sub-issues, native dependencies, Project #1 priority) are written for GitHub via the gh CLI. A tracker without native blocking falls back to a body convention.
Skip the map when charting surfaces no fog: if the way to the destination is already clear and the whole journey fits one session, the skill tells you to stop and decide how to proceed directly instead of creating tickets.
AO-HySPlans large efforts as decision-ticket maps on an issue tracker.
kashman001Reconciles backlog, memory, and docs, then writes a hand-off doc and catch-up prompt at session boundaries.
Fatih0234Plans large efforts as decision tickets on an issue tracker and resolves them one at a time.
cloudofgeorgePlan large multi-session efforts as decision tickets on an issue tracker.