wayfinder

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

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill wayfinder-tajo9128
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/tajo9128/BioDockify-Pharma-AI/tree/main/.agents/skills/wayfinder
Command: npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill wayfinder-tajo9128

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, claiming via assignment, and native blocking dependencies that render the frontier visually. - Incremental resolution: Sessions claim one frontier ticket, resolve it, record the answer as a resolution comment, and graduate newly specifiable fog into fresh tickets. - Use Case: A team facing a vague migration effort invokes Wayfinder to chart a map, fans out research subagents on open questions, and works through grilling and prototype tickets until every decision blocking execution is resolved. ## 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 Wayfinder with your loose idea to chart a map issue on the repo's issue tracker. It grills you to name the destination, then creates decision tickets as child issues that sessions resolve one at a time until the way is clear.

What is a decision ticket in issue-based planning?

A decision ticket is a child issue 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 execute the work it plans?

No, Wayfinder is planning by default: tickets resolve decisions, and the map is done when nothing remains to decide. An effort can override this in its Notes section to carry execution into the map itself.

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

Yes. Sessions claim tickets by assigning themselves before starting work, so concurrent sessions skip claimed tickets. Blocking uses the tracker's native dependency feature to keep the frontier visible.

What issue trackers does Wayfinder support?

Wayfinder is tracker-agnostic; the tracker doc's Wayfinding operations section defines how maps, child tickets, and blocking are expressed. If no tracker is provided, it defaults to a local-markdown tracker.