wayfinder

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

9|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Yassimba/loom --skill wayfinder-yassimba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/Yassimba/loom/tree/main/skills/wayfinder
Command: npx skills add https://github.com/Yassimba/loom --skill wayfinder-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, fuzzy efforts that exceed a single agent session lose context between sessions, leaving decisions scattered and progress untracked. This Skill turns a loose idea into a shared map of decision tickets on the repo's issue tracker, so every session orients to the destination and resolves one decision at a time. ## Core Features & Use Cases - Map charting: Names the destination, sketches unresolved fog into a Not-yet-specified section, and creates child decision tickets with blocking dependencies on the issue tracker. - Ticket resolution workflow: Claims one frontier ticket per session, resolves it via research, prototype, grilling, or task ticket types, then records the answer as a resolution comment and updates the map's Decisions-so-far index. - Scope and fog management: Distinguishes in-scope fog that graduates into tickets from out-of-scope work that is closed and documented, keeping the map honest. - Use Case: A team faces a vague data-structure migration too big for one session. The agent charts a map issue, creates research and grilling tickets, fires parallel research subagents, and subsequent sessions work the frontier until the way to the migration spec is clear. ## Quick Start Use the wayfinder skill to chart a decision-ticket map for this large migration idea on our 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, sketch unresolved questions into a Not-yet-specified section, and create decision tickets as child issues on the tracker. Each later session claims and resolves one frontier ticket until the way is clear.

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. It carries a wayfinder label of research, prototype, grilling, or task, and its answer is recorded as a resolution comment when closed.

Which issue trackers does wayfinder support?

The map, tickets, blocking, and frontier queries are tracker-specific and configured in ai-docs/agents/issue-tracker.md. Without configuration, it uses Beads when the br CLI is installed, otherwise local Markdown files.

Can multiple agent sessions work the same map in parallel?

Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. Blocking dependencies define the frontier of open, unblocked, unclaimed tickets that are safe to take.

When should I not use a wayfinding 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. Also avoid it for pure execution work, since wayfinder produces decisions, not deliverables.