Charts large ideas as issue-tracker maps of investigation tickets resolved one per session.
npx skills add https://github.com/vinzenz/workflows --skill wayfinder-vinzenz
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/vinzenz/workflows/tree/main/.agents/skills/wayfinder Command: npx skills add https://github.com/vinzenz/workflows --skill wayfinder-vinzenz
wayfinder:map issue with child tickets for each open question, wired with native blocking dependencies. - Ticket-driven resolution: Each ticket is typed (grilling, research, prototype, task) and marked HITL or AFK, claimed via assignment plus a timestamped claim comment, and resolved with a ## Resolution comment before closing. - Resumability and frontier tracking: State lives entirely on the tracker, so dead sessions are detected via stale claims and the frontier of unblocked, unclaimed tickets is always queryable. - Use Case: A team needs to decide the shape of a data migration. Wayfinder charts a map of grilling and research tickets on GitHub, and each agent session resolves exactly one ticket until the migration spec is fully decided. ## Quick Start Ask the agent to use wayfinder to chart your loosely defined project idea into a map of investigation tickets on the GitHub issue tracker.High-intent search queries and answers about installing and using this skill.
Use wayfinder to name the destination first, then map the frontier breadth-first into child issues on the tracker. Each ticket states one question sized to a single agent session, with a type (grilling, research, prototype, task) and HITL or AFK mode.
It drives GitHub's issue-dependencies API through gh-tool api, posting to /issues/{n}/dependencies/blocked_by with the blocker's numeric database id. The frontier is computed from open children with zero assignees and zero open blockers.
Yes, it has a local markdown fallback storing map.md and numbered ticket files under .wayfinder/<effort>/, using Status and Blocked by lines instead of labels and native dependencies. GitLab is documented as not yet usable due to missing dependency support.
No. Wayfinder produces decisions, not deliverables: it writes only to the tracker, docs/ specs and ADRs, and its own .wayfinder/ scratch directory. It explicitly never touches application source, migrations, or runtime configuration.
A claimed but unresolved ticket (assignee present, no Resolution comment) marks a dead session. The next session reads the Claim comment timestamp, judges staleness, unclaims the ticket, and re-claims it to resume work.
Use pathfinder when the effort has a structure to find — components and how they fit — and the risk is committing to details before the shape is agreed. Wayfinder fits when the work is a checklist of unknowns sharpened depth-first; never run both over the same effort.
Lento47Create, triage, label, and manage GitHub issues via gh CLI or REST API.
nico0695Interviews the user in rounds to surface and resolve open decisions in a plan.
mattpocockInterviews a plan or design while generating ADRs and glossary documentation.
SorraTheOrcGenerate structured effort estimates and risk assessments from plan_complete issues.