wayfinder

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

2|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/skills --skill wayfinder-iskenkenya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/IsKenKenYa/skills/tree/main/skills/engineering/wayfinder
Command: npx skills add https://github.com/IsKenKenYa/skills --skill wayfinder-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a project idea is too big for a single agent session and the path forward is unclear, this Skill breaks the fog into a shared map of decision tickets on the repo's issue tracker, then resolves them one at a time until the route to the destination is clear. ## Core Features & Use Cases - Map charting: Names the destination, sketches unresolved questions into a "Not yet specified" fog section, and creates child-issue tickets labeled by type (research, prototype, grilling, task). - Frontier tracking: Uses the tracker's native blocking relationships and assignment-based claiming so concurrent sessions know which tickets are open, unblocked, and unclaimed. - Resolution workflow: Resolves one ticket per session, records answers as resolution comments, closes issues, and appends one-line gists to the map's Decisions-so-far index. - Use Case: You have a vague idea like "migrate our data layer to a new schema." Invoke the Skill to grill out the destination, create a map issue with research and grilling tickets, then work through them across multiple sessions until a spec is ready to hand off. ## Quick Start Ask the agent to chart a wayfinder map for your loosely defined project idea on this 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 break down a project too big for one agent session?▼

Chart a wayfinder map: name the destination, create a map issue labeled wayfinder:map, and add child tickets for each decision you can already state precisely. Then resolve one ticket per session until no decisions remain before execution.

What is a decision ticket in issue-based planning?▼

A decision ticket is a child issue 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 agent session.

Which issue trackers does this planning workflow support?▼

The workflow is tracker-agnostic but requires child issues, labels, and ideally native blocking dependencies. The tracker-specific operations come from a tracker doc; if none is provided, it defaults to a local-markdown tracker.

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

Yes. Sessions claim tickets by assigning them before starting work, so concurrent sessions skip claimed tickets. Blocking relationships define which open tickets form the takeable frontier.

When should I not create a wayfinder map?▼

Skip the map when breadth-first grilling surfaces no fog—meaning the path to the destination is already clear and the whole effort fits in one session. In that case, proceed directly with the work instead.