wayfinder

Plans large multi-session efforts as issue-tracker maps of investigation tickets.

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill wayfinder-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/mmnavarr/harness/tree/main/skills/wayfinder
Command: npx skills add https://github.com/mmnavarr/harness --skill wayfinder-mmnavarr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large, ambiguous efforts exceed what a single agent session can hold, leaving decisions scattered and progress untracked. This Skill turns a vague idea into a shared map of investigation tickets on the repo's issue tracker, then resolves them one at a time until the path to the destination is clear. ## Core Features & Use Cases - Map charting: Names the destination, sketches unresolved questions into a fog-of-war section, and creates child tickets with blocking dependencies on the issue tracker. - Ticket-driven resolution: Claims one ticket per session, resolves it via research, prototyping, grilling, or manual tasks, and records the answer as a resolution comment. - Frontier management: Tracks open, unblocked, unclaimed tickets as the working frontier and graduates newly specifiable fog into fresh tickets as decisions land. - Use Case: You need to plan a data-structure migration too big for one session. Invoke the Skill to create a map issue, spawn research and grilling tickets, and work through them across multiple sessions until every decision is made. ## Quick Start Ask the agent to chart a wayfinder map for your loosely defined project idea on this repo's 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 the Skill with your loose idea to chart a map: it names the destination, creates a labelled map issue, and spawns child tickets for each open decision. Subsequent sessions resolve one ticket at a time until the way is clear.

How do I break down ambiguous work into investigation tickets?▼

Run a breadth-first grilling session to surface open decisions, then create one child issue per sharp question, each sized to a single 100K-token session. Questions you cannot yet phrase precisely stay in the map's Not yet specified section until the frontier advances.

What issue tracker features does this planning workflow require?▼

It requires labels, child issues, assignees for claiming tickets, and native blocking dependencies so the frontier renders visually. Trackers lacking native blocking fall back to a body convention, and absent any tracker doc it defaults to local markdown files.

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

Yes, sessions run unblocked tickets in parallel. Each session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets, and each session resolves at most one ticket.

When should I not use a ticket map for planning?▼

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 when you want execution, since the default mode produces decisions, not deliverables.