wayfinder

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill wayfinder-the-focus-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/The-Focus-AI/walking-thoughts/tree/main/.agents/skills/wayfinder
Command: npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill wayfinder-the-focus-ai

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 defined destination. This Skill 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 Creation: Charts a loose idea into a single map issue (labelled wayfinder:map) with a destination, notes, decisions-so-far index, and fog-of-war sections. - Decision Tickets: Breaks work into child issues typed as research, prototype, grilling, or task, with native blocking relationships defining the workable frontier. - Session-Based Resolution: Claims, resolves, and closes one ticket per session, recording answers as resolution comments and graduating newly specifiable fog into fresh tickets. - Use Case: A team facing a vague data-migration effort invokes the Skill to grill out the destination, create a map with research and grilling tickets, then work through them across multiple sessions until every decision blocking the migration is resolved. ## Quick Start Ask the agent to chart a map for your loosely defined effort, or invoke it with an existing map issue 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 the Skill with your loose idea to chart a map: it grills out the destination, creates a map issue labelled wayfinder:map, and files the specifiable decisions as child tickets. Subsequent sessions work through one ticket at a time until the route is clear.

How do decision tickets work on an issue tracker?

Each ticket is a child issue of the map containing a single question sized to one agent session. Tickets carry a wayfinder type label (research, prototype, grilling, or task), are claimed by assignment, and are resolved with a comment before closing.

What issue trackers does the wayfinding workflow support?

The Skill is tracker-agnostic and consults the tracker documentation provided to the agent for how the repo expresses maps, child tickets, and blocking. If no tracker is provided, it defaults to a local-markdown tracker.

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

Yes, unblocked tickets can be worked in parallel by different sessions. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets and pick from the remaining open, unblocked frontier.

When should I not create a wayfinding 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. The Skill also plans rather than executes by default, so direct build work belongs outside it.