wayfinder

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/falentio/cimi --skill wayfinder-falentio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/wayfinder
Command: npx skills add https://github.com/falentio/cimi --skill wayfinder-falentio

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 breaks that fog into a shared map of decision tickets on the repo's issue tracker, resolving them one at a time until the route is clear. ## Core Features & Use Cases - Map charting: Creates a single map issue (labelled wayfinder:map) with a Destination, Notes, Decisions-so-far index, Not-yet-specified fog, and Out-of-scope sections. - Typed decision tickets: Each child issue is a research, prototype, grilling, or task ticket, claimed by assignment and ordered by native blocking relationships so the frontier is visible in the tracker UI. - Session-bounded resolution: Resolves at most one ticket per session, records answers as resolution comments, and graduates newly specifiable fog into fresh tickets. - Use Case: A team facing a vague data-migration effort invokes Wayfinder to name the destination, fan out the open decisions breadth-first, and work the resulting tickets across parallel sessions until nothing remains undecided. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your loosely defined project idea on the 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 the loose idea to chart a map: it names the destination, runs a breadth-first grilling to surface open decisions, then creates a map issue and child decision tickets on the issue tracker. Each later session resolves one ticket at a time until the way is clear.

What is a decision ticket in issue tracker planning?

A decision ticket is a child issue of the map whose body states one question sized to a single agent session. It carries a type label (research, prototype, grilling, or task) and is resolved by posting a resolution comment and closing the issue.

Does Wayfinder require a specific issue tracker?

Wayfinder works with whatever issue tracker is configured for the repo, using its native labels, child issues, assignment, and blocking relationships. If no tracker is provided, it defaults to a local-markdown tracker and asks you to run the setup command.

How does Wayfinder handle work that cannot be ticketed yet?

Questions that cannot yet be phrased precisely go into the map's Not yet specified section as fog of war. As tickets resolve and clear the fog, each specifiable patch graduates into a fresh ticket and is removed from that section.

When should I not use Wayfinder for a task?

Skip Wayfinder when the way to the destination is already clear and the whole journey fits in one session; charting a map adds overhead with no benefit. It is also planning-first by default, so direct execution work belongs outside the map unless the effort's Notes override this.