wayfinder

Plan large efforts as decision tickets on an issue tracker and resolve them incrementally.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/julianckt/adoptarun --skill wayfinder-julianckt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/julianckt/adoptarun/tree/main/.agents/skills/wayfinder
Command: npx skills add https://github.com/julianckt/adoptarun --skill wayfinder-julianckt

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 planned and 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: Child issues are classified as research, prototype, grilling, or task tickets, each sized to one agent session and wired with native blocking relationships. - Frontier-driven execution: Sessions claim open, unblocked, unassigned tickets, resolve them with resolution comments, and graduate newly specifiable fog into fresh tickets. - Use Case: A team facing a vague data-migration effort invokes Wayfinder to chart a map of open decisions, then works through research and grilling tickets across multiple sessions until the route to the migration spec is fully decided. ## Quick Start Ask the agent to chart a wayfinder map for your loosely defined project idea so it can break the effort into 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 undecided areas as fog, and creates decision tickets as child issues on the issue tracker. Each later session resolves one ticket at a time until the route is clear.

What is a decision ticket in issue-based planning?

A decision ticket is a child issue of the map whose body states one question sized to a single agent session. It carries a type label such as research, prototype, grilling, or task, and is resolved by posting a resolution comment and closing the issue.

Does Wayfinder work with GitHub Issues or other trackers?

Wayfinder is tracker-agnostic: the map, child tickets, blocking, and frontier queries are expressed through whatever issue tracker the repo provides, using native blocking relationships where available. Without a configured tracker it defaults to a local-markdown tracker.

When should I not use a wayfinding map?

Skip the map when charting surfaces no fog, meaning the way to the destination is already clear and the whole journey fits in one session. Wayfinder is for planning decisions, not executing deliverables, so direct build work should be handed off.

How does Wayfinder handle work outside the project scope?

Work beyond the destination is recorded in the map's Out of scope section rather than as fog or tickets. Mis-scoped tickets are closed with a one-line note linking them, and they never graduate back unless the destination is redrawn.