wayfinder

Plans large efforts as decision tickets on an issue tracker and resolves them one at a time.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill wayfinder-fatih0234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/Fatih0234/mattpocock-skills-pi/tree/main/skills/engineering/wayfinder
Command: npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill wayfinder-fatih0234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large efforts that exceed a single agent session arrive wrapped in uncertainty: the path from a loose idea to a finished spec, decision, or change 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 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, with child issues as decision tickets. - Typed tickets with blocking: Each ticket is typed as research, prototype, grilling, or task, claimed by assignment, and ordered via the tracker's native blocking relationships so the actionable frontier is always visible. - Parallel research delegation: Research tickets are delegated to isolated researcher subagents that write report artifacts, while the parent session records resolutions and closes tickets. - Use Case: You need to plan a data-structure migration too big for one session. Invoke wayfinder to chart a map: it grills you to name the destination, fans out breadth-first to surface open decisions, creates tickets, wires blocking edges, and then resolves one ticket per session until the route is clear. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your large, loosely-defined effort, or invoke it with an existing map URL to work through the next open decision ticket.

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. It grills you to name the destination, maps the open decisions breadth-first, creates a map issue with child decision tickets, and wires blocking edges. Each later session resolves one ticket until the route is clear.

How do decision tickets work on the issue tracker?▼

Each ticket is a child issue of the map with a question body and a type label: research, prototype, grilling, or task. A session claims a ticket by assigning it, resolves it, posts a resolution comment, closes it, and appends a gist to the map's Decisions-so-far section.

What issue trackers does wayfinder support?▼

Wayfinder is tracker-agnostic but requires labels, child issues, assignment, and ideally native blocking relationships. The tracker is supplied by a separate setup skill; if none is provided, it falls back to a local-markdown tracker.

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

Yes. Tickets are claimed by assignment before work begins, so concurrent sessions skip claimed tickets. The frontier is the set of open, unblocked, unclaimed tickets, and research tickets can be delegated to parallel researcher subagents.

When should I not use wayfinder for planning?▼

Skip it when the way to the destination is already clear and the whole effort fits in one session; charting would add overhead with no fog to clear. It also produces decisions, not deliverables, so execution work belongs to a follow-up step.