wayfinder

Plan large multi-session work as decision tickets on an issue tracker.

3|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ever-just/agentskills --skill wayfinder-ever-just
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/ever-just/agentskills/tree/main/skills/wayfinder
Command: npx skills add https://github.com/ever-just/agentskills --skill wayfinder-ever-just

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-horizon initiatives stall because no single agent session can finish them and nothing tracks open decisions between sessions. Wayfinder turns a loose, oversized idea into a shared map of decision tickets on an issue tracker (or local markdown files), so progress survives across as many sessions as it takes. ## Core Features & Use Cases - Map-based planning: Creates a single map issue (labeled wayfinder:map) holding the destination, notes, decisions-so-far index, fog-of-war items, and out-of-scope rulings, with child tickets sized to one session each. - Typed decision tickets: Classifies work as research, prototype, grilling, or task tickets, with HITL/AFK designation, native blocking edges, and claim-by-assignment so concurrent sessions never collide. - Frontier-driven execution: Resolves one ticket per session, records answers as resolution comments, graduates newly specifiable fog into tickets, and closes mis-scoped work as out of scope. - Use Case: You have a vague initiative like migrating a data model or drafting a product spec. Invoke the skill to chart a map of open decisions on GitHub Issues, then work through one ticket per session until the route to the destination is clear. ## Quick Start Ask the agent to chart a wayfinder map for your loosely defined initiative, naming the destination and the issue tracker to use.

Frequently Asked Questions about wayfinder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a project too big for one agent session?▼

Chart a wayfinder map: name the destination through a grilling session, map the frontier breadth-first, then create one decision ticket per open question as child issues. Each later session claims and resolves exactly one ticket until no decisions remain.

How do I track decisions across multiple agent sessions?▼

Use a single map issue labeled wayfinder:map whose Decisions-so-far section indexes one line per closed ticket with a link. Each ticket holds its full resolution as a comment, so any new session loads the map and continues from the frontier.

Can I use wayfinder without GitHub Issues or another tracker?▼

Yes. When the project has no issue tracker, the skill falls back to a local-markdown tracker: a wayfinder/ directory with one numbered file per ticket and a wayfinder/map.md file, using file references in place of native links and blocking edges.

What is the difference between a wayfinder ticket and fog of war?▼

A ticket is a question you can already state precisely, even if blocked. Fog of war covers suspected decisions you cannot yet phrase sharply; it lives in the map's Not yet specified section and graduates into tickets as the frontier advances.

When should I not use wayfinder for a task?▼

Skip it when the way to the destination is already clear and the whole journey fits in one session. Wayfinder is planning by default, so it produces decisions, not deliverables, and never resolves more than one ticket per session.