wayfinder

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

2|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill wayfinder-ankaboot-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/wayfinder
Command: npx skills add https://github.com/ankaboot-source/boucle --skill wayfinder-ankaboot-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, ambiguous efforts are too big for a single agent session and lack a clear path from idea to destination. Wayfinder breaks such work into a shared map of decision tickets on the repo's issue tracker, resolving them one at a time until the route forward is clear. ## 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 sections. - Typed decision tickets: Splits work into child issues typed as research, prototype, grilling, or task, with native blocking relationships defining the actionable frontier. - Incremental resolution: Claims, resolves, and closes one ticket per session, recording answers as resolution comments and graduating newly specifiable fog into fresh tickets. - Use Case: Given a vague feature request in a GitHub issue, chart a map of research and prototype tickets, then work through them across multiple CI agent sessions until a spec is ready to hand off. ## Quick Start Ask the agent to chart a wayfinder map for the loosely defined initiative described in this issue, then work through its frontier tickets one per session.

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 large ambiguous project into manageable agent tasks?

Chart a wayfinder map: name the destination, sweep the space breadth-first for open decisions, and create typed child tickets (research, prototype, task) on the issue tracker. Resolve one ticket per session until no decisions remain.

What is the difference between a decision ticket and a regular task ticket?

A decision ticket resolves a question whose answer is a decision, recorded as a resolution comment when closed. A task ticket performs manual work that unblocks a decision, such as provisioning access, and earns its place only by unblocking.

Can wayfinder run autonomously in CI without a human in the loop?

Yes, in CI mode all tickets are driven by the agent alone. Grilling sessions are disabled; the agent derives decisions from the issue body and codebase, closing unresolvable tickets as needs-info with the unanswered questions recorded.

How does wayfinder handle work that cannot be specified yet?

Unspecifiable but in-scope questions go in the map's Not yet specified section as fog of war. As tickets resolve and clear the fog, each patch graduates into concrete tickets; work beyond the destination is ruled out of scope instead.

When should I not use a wayfinder map?

Skip the map when the way to the destination is already clear and the whole journey fits in one session. In that case, document the inferred route inline and proceed directly without creating map or ticket issues.