wayfinder

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

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill wayfinder-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/engineering/wayfinder
Command: npx skills add https://github.com/reddb-io/red-skills --skill wayfinder-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large efforts often exceed what a single agent session can hold, leaving the path from a loose idea to a finished destination unclear. This Skill charts that path as a shared map of decision tickets on the repo's issue tracker, then resolves them one at a time until the way forward is fully decided. ## Core Features & Use Cases - Map-based planning: Creates a single map issue (labelled wayfinder:map) that indexes decisions, tracks fog-of-war items not yet specifiable, and records out-of-scope rulings. - Typed decision tickets: Breaks work into research, prototype, grilling, and task tickets, each sized to one agent session, with native tracker blocking to define the workable frontier. - HITL/AFK routing: Declares human-in-the-loop ticket types so autonomous queues never pick up decisions that require a live human exchange. - Use Case: You have a vague idea for a data-structure migration too big for one session. Invoke the Skill to name the destination, fan out the open decisions into tickets on GitHub Issues, fire research subagents in parallel, and then work through the frontier one ticket per session until the route is clear. ## Quick Start Ask the agent to chart a wayfinder map for your large idea, or point it at an existing map issue URL to resolve the next 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 work too big for one agent session?▼

Chart a wayfinder map: name the destination, run a breadth-first grilling to surface open decisions, then create child decision tickets on the issue tracker. Resolve one ticket per session until no decisions remain before execution.

How do I break a vague project idea into trackable issues?▼

Create a map issue labelled wayfinder:map holding the destination, notes, and decisions index, then file each sharp question as a child ticket. Questions you cannot yet phrase precisely stay in the map's Not yet specified section until the frontier advances.

Does wayfinder work with GitHub Issues dependencies?▼

Yes, blocking uses the tracker's native dependency relationship so the frontier renders visually in the tracker UI. Trackers lacking native blocking fall back to a body convention, and a local-markdown tracker is the default when none is provided.

How are human-in-the-loop tickets kept out of autonomous queues?▼

The install_type_labels tool creates the wayfinder type labels and declares grilling and prototype as HITL types in .red/config.yaml. Declared HITL tickets park as ready-for-human instead of entering the AFK queue when unblocked.

When should I not use a wayfinder map?▼

Skip the map when charting surfaces no fog, meaning the way to the destination is already clear and the whole journey fits in one session. Wayfinder is planning by default, so it produces decisions, not deliverables.