Plan large efforts as decision tickets on an issue tracker and resolve them incrementally.
npx skills add https://github.com/tlipoca9/dotfiles --skill wayfinder-tlipoca9
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/tlipoca9/dotfiles/tree/main/home/dot_agents/skills/wayfinder Command: npx skills add https://github.com/tlipoca9/dotfiles --skill wayfinder-tlipoca9
wayfinder:map) that indexes decisions, tracks fog-of-war items not yet specifiable, and records out-of-scope rulings. - Typed decision tickets: Each child ticket is labelled research, prototype, grilling, or task, distinguishing HITL conversations from AFK agent-driven work. - Frontier and blocking management: Uses the tracker's native dependency relationships so open, unblocked, unclaimed tickets form a visible frontier that parallel sessions can claim safely. - Use Case: You need to plan a data-structure migration too big for one session. Invoke the Skill with the idea; it grills you to name the destination, charts the map, creates the first tickets, fires research subagents, and later sessions resolve one ticket at a time, recording each answer as a resolution comment. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your loosely defined project idea on the repo's issue tracker.High-intent search queries and answers about installing and using this skill.
Invoke the Skill with your loose idea. It names the destination through a grilling conversation, creates a map issue labelled wayfinder:map, and files the specifiable open questions as child decision tickets to resolve one per session.
The Skill charts tickets breadth-first across the problem space, labelling each as research, prototype, grilling, or task. Questions too vague to state precisely stay in the map's Not yet specified section until resolving tickets makes them sharp.
The map and tickets live on the repo's configured issue tracker, which should provide child issues, labels, assignment, and native blocking. If no tracker is provided, the Skill defaults to a local-markdown tracker.
Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. The frontier of open, unblocked, unclaimed tickets stays visible through the tracker's native blocking UI.
Skip the map when the way to the destination is already clear and the whole effort fits one session; the Skill stops and asks how to proceed instead. It also produces decisions, not deliverables, unless the map's Notes explicitly carry execution into it.
Evolutionary-LeadershipInterviews users to stress-test ideas and records outcomes in issue tracker.
kashman001Reconciles backlog, memory, and docs, then writes a hand-off doc and catch-up prompt at session boundaries.
mst-software-vnConverts loose ideas into sequenced investigation tickets tracked in a markdown decision map.
telefrekImplement small code changes with TDD and minimal setup.