wayfinder

Plans large efforts as decision tickets on an issue tracker and resolves them incrementally.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/ZubairImtiaz3/Safar-E-Iman-Portal --skill wayfinder-zubairimtiaz3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/ZubairImtiaz3/Safar-E-Iman-Portal/tree/main/.agents/skills/wayfinder
Command: npx skills add https://github.com/ZubairImtiaz3/Safar-E-Iman-Portal --skill wayfinder-zubairimtiaz3

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 concrete destination. Wayfinder charts that path as a shared map of decision tickets on the repo's issue tracker, resolving them one at a time until the way forward 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 workable frontier. - Session-safe claiming and resolution: Claims tickets by assignment, resolves at most one ticket per session, and records answers as resolution comments linked from the map. - Use Case: A team facing a vague data-migration effort invokes Wayfinder to name the destination, fan out the open decisions into tickets, fire research subagents in parallel, and then work through the frontier ticket by ticket across multiple sessions. ## Quick Start Ask the agent to chart a wayfinder 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: it names the destination, grills breadth-first to surface open decisions, creates a map issue labelled wayfinder:map, and files the specifiable questions as child tickets. Later sessions work through the frontier one ticket at a time.

How do decision tickets work on the issue tracker?

Each ticket is a child issue of the map with a Question body and a wayfinder type label: research, prototype, grilling, or task. Tickets are claimed by assignment, ordered by native blocking relationships, and resolved with a resolution comment before closing.

What issue trackers does Wayfinder support?

Wayfinder is tracker-agnostic but requires labels, child issues, assignees, and ideally native blocking relationships. The tracker should be provided via its documentation; if none is provided, it defaults to a local-markdown tracker.

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

Yes. Tickets are claimed by assigning them before work begins, so concurrent sessions skip claimed tickets. The frontier is the set of open, unblocked, unclaimed child issues, and each session resolves at most one ticket, except research tickets.

When should I not use a wayfinder map?

Skip the map when the way to the destination is already clear and the whole journey fits in one session. Wayfinder also produces decisions, not deliverables, so it is the wrong tool when the work is execution rather than planning.