wayfinder

Plans large efforts as decision tickets on an issue tracker and resolves them one per session.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill wayfinder-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/wayfinder
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill wayfinder-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, fuzzy efforts are too big for a single agent session, and the path from idea to destination is unclear. Wayfinder turns that fog into a shared map of decision tickets on the repo's issue tracker, so work is planned, tracked, and resolved incrementally across sessions. ## 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 child ticket is one of research, prototype, grilling, or task, with HITL or AFK modes, native blocking relationships, and claim-by-assignment for concurrent sessions. - Frontier-driven execution: Sessions pick the next open, unblocked, unclaimed ticket, resolve it, record the answer as a resolution comment, and graduate newly specifiable fog into fresh tickets. - Use Case: A team needs to decide on a data-structure migration spanning many unknowns. Wayfinder charts a map of research and grilling tickets, fires research subagents in parallel, and works the frontier one decision per 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 the fog of war, and creates decision tickets as child issues on the tracker. Each later session resolves one ticket at a time until the way is clear.

What is a decision ticket in wayfinding?

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

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 uses the tracker's native dependency relationship, and the frontier is the open, unblocked, unclaimed children.

What happens if no issue tracker is configured?

Wayfinder consults the repo's tracker documentation for how maps, tickets, and blocking are expressed. If no tracker is configured, it defaults to a local-markdown tracker for storing the map and its tickets.

When should I not use wayfinding for a task?

Skip wayfinding when the path to the destination is already clear and the whole journey fits in one session — charting surfaces no fog. It is also planning by default, so pure execution work should be handed off rather than mapped.