wayfinder

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

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill wayfinder-kunj-sharma03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/skills-main/skills/engineering/wayfinder
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill wayfinder-kunj-sharma03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large initiatives are too big for a single agent session and too vague to plan upfront. Wayfinder breaks a loose idea into a shared map of decision tickets on your repo's issue tracker, so work progresses one resolved decision at a time instead of stalling in ambiguity. ## 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 items, with child issues as tickets. - Typed decision tickets: Classifies work as research, prototype, grilling, or task tickets, each sized to one agent session, with native tracker blocking to define the actionable frontier. - Two invocation modes: Chart a new map from a loose idea, or work through an existing map by claiming, resolving, and closing one ticket per session while graduating newly specifiable fog. - Use Case: You need to plan a data-structure migration spanning weeks. Wayfinder creates a map issue, files research and grilling tickets for open questions, wires blocking dependencies, and resolves them session by session until the route to the migration spec is clear. ## Quick Start Ask the agent to chart a wayfinder map for your large initiative, describing the destination you want to reach and the issue tracker to use.

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, files decision tickets as child issues on your issue tracker, wires blocking dependencies, and then resolves one ticket per session until the route is clear.

What is a decision ticket in wayfinding?

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

Does wayfinder work with GitHub Issues or other trackers?

Wayfinder is tracker-agnostic but requires tracker-specific setup, typically via the setup-matt-pocock-skills skill. It uses the tracker's native labels, child issues, assignees, and blocking relationships, falling back to local markdown if no tracker is provided.

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. The frontier — open, unblocked, unclaimed tickets — defines what is safe to pick up in parallel.

When should I not use wayfinder for planning?

Skip wayfinder when the way to the destination is already clear and the whole effort fits in one session — charting a map adds overhead with no benefit. It is also planning-only by default, so pure execution work belongs elsewhere.