wayfinder

Plans large efforts as decision tickets on an issue tracker and resolves them incrementally.

7|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/J0Jng/MathModelingAgents --skill wayfinder-j0jng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/J0Jng/MathModelingAgents/tree/main/.claude/skills/engineering/wayfinder
Command: npx skills add https://github.com/J0Jng/MathModelingAgents --skill wayfinder-j0jng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, ambiguous efforts often exceed what a single agent session can hold, leaving the path from idea to destination unclear. Wayfinder turns that fog into a shared map of decision tickets on the repo's issue tracker, so work is resolved one decision at a time instead of being charged at blindly. ## 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 boundaries. - Typed decision tickets: Each ticket is a child issue typed as research, prototype, grilling, or task, with HITL/AFK modes, native blocking dependencies, and claim-by-assignment for concurrent sessions. - Two invocation modes: Chart a new map from a loose idea, or work through an existing map by claiming and resolving one frontier ticket per session. - Use Case: A team facing a vague migration effort invokes Wayfinder to name the destination, fan out the open decisions into tickets, fire research subagents in parallel, and then resolve tickets session by session until the route is clear. ## Quick Start Ask the agent to chart a wayfinder map for your loosely defined effort, naming the destination and letting it create the first decision tickets on the 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 Wayfinder with your loose idea to chart a map: it names the destination, sketches unspecified fog, and creates decision tickets as child issues on the tracker. Each later session claims and resolves one frontier ticket until the way is clear.

What is a decision ticket in issue-tracker planning?▼

A decision ticket is a child issue of the map whose resolution is a decision rather than a build slice. Each carries a type label — research, prototype, grilling, or task — and is sized to fit one agent session.

Does Wayfinder require a specific issue tracker?▼

Wayfinder works with whatever issue tracker is configured for the repo, using its native labels, child issues, and blocking relationships. If no tracker is provided, it defaults to a local-markdown tracker.

Can multiple agent sessions work on the same map concurrently?▼

Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. Blocking dependencies define which open tickets form the takeable frontier.

When should I not use Wayfinder?▼

Skip it when the way to the destination is already clear and the whole journey fits one session — charting a map adds overhead with no benefit. It is also planning-oriented by default, so pure execution work belongs elsewhere.