wayfinder

Plan large multi-session efforts as decision-ticket maps on an issue tracker.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/MaksymilianCzadowski/skills --skill wayfinder-maksymilianczadowski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/MaksymilianCzadowski/skills/tree/main/skills/engineering/wayfinder
Command: npx skills add https://github.com/MaksymilianCzadowski/skills --skill wayfinder-maksymilianczadowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large efforts often exceed what a single agent session can hold, leaving the path from idea to destination unclear. This Skill breaks that fog into a shared map of decision tickets on your repo's issue tracker, so work progresses one resolved decision at a time across many sessions. ## Core Features & Use Cases - Map-based planning: Creates a single map issue (labelled wayfinder:map) holding the destination, notes, decisions-so-far index, and fog-of-war sections, with child issues as tickets. - Typed decision tickets: Classifies tickets as research, prototype, grilling, or task, distinguishing HITL work from AFK work an agent can drive alone. - Frontier and blocking management: Uses the tracker's native dependency relationships so only open, unblocked, unclaimed tickets form the actionable frontier. - Use Case: You need to plan a data-structure migration too big for one session. Invoke the skill to chart a map, spawn research subagents in parallel, then resolve one ticket per session until the route is clear. ## 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?▼

Chart a wayfinder map: name the destination through a grilling session, create a map issue labelled wayfinder:map, then add child decision tickets wired with blocking relationships. Resolve one ticket per session until no decisions remain.

What is a decision ticket in issue-tracker 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 100K-token agent session.

Does wayfinder work with any issue tracker?▼

Wayfinder is tracker-agnostic but expects the tracker to be provided via setup; its operations section defines how maps, child tickets, and blocking are expressed. Without a provided tracker, it defaults to a local-markdown tracker.

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. Research tickets can also be resolved in parallel by subagents on throwaway branches.

When should I not use a decision-ticket 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. In that case, ask the user how they would like to proceed directly.