wayfinder

Plans large efforts as decision tickets tracked in markdown files under plans/.

Updated Jan 19, 2023
One-click install
npx skills add https://github.com/inkfin/dotfiles --skill wayfinder-inkfin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayfinder
Source: https://github.com/inkfin/dotfiles/tree/main/dot_agents/skills/exact_wayfinder
Command: npx skills add https://github.com/inkfin/dotfiles --skill wayfinder-inkfin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large efforts often exceed what a single agent session can hold, leaving the path from idea to destination unclear. This Skill charts that path as a shared map of decision tickets under plans/, resolving them one at a time until the way forward is fully specified. ## Core Features & Use Cases - Map-based planning: Creates a plans/<effort-slug>/map.md index with Destination, Notes, Decisions-so-far, fog (Not yet specified), and Out of scope sections. - Decision tickets: Tracks work as numbered markdown tickets with Type (grilling, research, prototype, task), Status, and Blocked-by dependency wiring, claimed before work to support concurrent sessions. - HITL/AFK ticket routing: Distinguishes human-in-the-loop tickets (grilling, prototype) from agent-alone work (research), firing research tickets as parallel subagents. - Use Case: You have a vague, multi-week migration idea. Invoke the Skill to grill the destination into focus, chart a map of sharp decision tickets, then work the frontier one ticket per session until the map hands off cleanly to spec-writing and implementation. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your loosely defined project idea, or point it at an existing plans/<effort>/map.md to work the next open ticket.

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 wayfinder skill with your loose idea. It grills the destination into focus, creates a map.md index under plans/<effort-slug>/, and writes numbered decision tickets under issues/ that get resolved one per session until the path is clear.

How do decision tickets track dependencies and status?

Each ticket file carries Type, Status (ready, claimed, done), and a Blocked-by line naming prerequisite tickets. A ticket is on the frontier when it is ready, unclaimed, and all blockers are done; sessions claim tickets before starting work.

Can multiple agent sessions work on the same plan concurrently?

Yes. Tickets are claimed by setting Status to claimed before work begins, so concurrent sessions skip them. Research tickets may also run in parallel as subagents, while all other tickets resolve one per session.

What is the difference between grilling, research, prototype, and task tickets?

Grilling tickets resolve decisions through live human conversation, research tickets surface facts the agent gathers alone, prototype tickets produce cheap artifacts for humans to react to, and task tickets cover manual work that unblocks a decision.

When should I not use map-based ticket planning?

Skip it when the whole journey fits in one session with no fog; the skill itself stops and suggests proceeding directly to specification. It also produces decisions, not deliverables, so execution work belongs in downstream implementation steps.