wayfinder

Plans large efforts as decision-ticket maps on an issue tracker.

1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/jwh3times/holland-vip --skill wayfinder-jwh3times
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/wayfinder
Command: npx skills add https://github.com/jwh3times/holland-vip --skill wayfinder-jwh3times

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, ambiguous efforts often exceed what a single agent session can hold, leaving teams without a clear path from a loose idea to a defined destination. Wayfinder turns that fog into a shared map of decision tickets on the repo's issue tracker, resolved one at a time until the route is clear. ## 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: Breaks work into child issues typed as research, prototype, grilling, or task, with native blocking relationships defining the actionable frontier. - Session-safe workflow: Claims tickets by assignment, resolves at most one ticket per session, and records answers as resolution comments so concurrent sessions never collide. - Use Case: A team facing a vague migration effort invokes Wayfinder to chart a map, fans out research subagents on open questions, and works the frontier ticket by ticket until every decision blocking execution is resolved. ## Quick Start Ask the agent to chart a wayfinder map for your loosely defined initiative, naming the destination it should find its way toward.

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 the loose idea to chart a map: it names the destination, sketches unspecifiable questions into a fog section, and creates decision tickets as child issues on the repo's issue tracker. Each later session resolves one ticket at a time until the route 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 work with any issue tracker?▼

Wayfinder is tracker-agnostic but expects the tracker to support labels, child issues, assignees, and ideally native blocking relationships. Trackers without native blocking fall back to a body convention, and a local-markdown tracker is the default.

Can multiple agent sessions work 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 — open, unblocked, unclaimed tickets — is what any session may pick up next.

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 effort fits in one session. Wayfinder also produces decisions, not deliverables, unless an effort's Notes explicitly carry execution into the map.