wayfinder

Plans large multi-session efforts as issue-tracker maps of investigation tickets resolved one at a time.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill wayfinder-sevwren
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/CLAUDE/skills/engineering/wayfinder
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill wayfinder-sevwren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, ambiguous efforts often exceed what a single agent session can hold, leaving decisions scattered and progress untracked. This Skill turns a loose idea into a shared map of investigation tickets on your issue tracker, so the route to the destination becomes visible and each decision is resolved one ticket at a time. ## Core Features & Use Cases - Map-based planning: Creates a single map issue (labelled wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope sections. - Typed tickets: Breaks work into research, prototype, grilling, and task tickets, each sized to one agent session, with native blocking relationships defining the frontier. - Two invocation modes: Chart a new map from a loose idea, or work through an existing map by claiming and resolving one ticket per session. - Use Case: You need to plan a data-structure migration too big for one session. Invoke the Skill to grill out the destination, chart the open decisions as tickets, then resolve them across multiple sessions until the way is clear. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your loosely defined project idea on the repo's issue tracker.

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?▼

Invoke the wayfinder skill with your loose idea. It runs a grilling session to name the destination, maps the open decisions breadth-first, then creates a map issue and child tickets on your issue tracker that later sessions resolve one at a time.

How does wayfinder track decisions across multiple sessions?▼

Each decision lives in exactly one ticket, and the map issue keeps a Decisions-so-far index linking to closed tickets with one-line gists. Every session loads the low-resolution map first, then zooms into ticket detail only as needed.

What issue trackers does wayfinder support?▼

Wayfinder is tracker-agnostic: the map, child tickets, blocking, and frontier queries are expressed through whatever tracker doc is provided for the repo. If no tracker is provided, it defaults to a local-markdown tracker.

Can multiple sessions work on the same map in parallel?▼

Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. The frontier is the set of open, unblocked, unclaimed child issues, and blocking uses the tracker's native dependency relationships.

When should I not use wayfinder for planning?▼

Skip it when the way to the destination is already clear and the whole journey fits in one session. If charting surfaces no fog, the skill stops and asks how you want to proceed instead of creating a map.