Plan large efforts as decision tickets on an issue tracker and resolve them incrementally.
npx skills add https://github.com/marjorg/setup --skill wayfinder-marjorg
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/archive/0-matt/wayfinder Command: npx skills add https://github.com/marjorg/setup --skill wayfinder-marjorg
wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope sections. - Typed decision tickets: Splits work into research, prototype, grilling, and task tickets, each sized to one agent session, with native blocking relationships defining the workable frontier. - Two invocation modes: Chart a new map from a loose idea, or work through an existing map by claiming and resolving one ticket per session. - Use Case: You need to plan a data-structure migration too big for one session. Invoke the skill with the idea, and it grills you to name the destination, creates the map and initial tickets, fires research subagents, and leaves a clear frontier for future sessions. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your large, loosely-defined effort 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 to chart a map: it names the destination through grilling, creates a map issue on the tracker, and files the decisions you can already specify as child tickets. Future sessions then resolve one ticket at a time until the way is clear.
A decision ticket is a child issue of the map whose resolution is a decision rather than a build deliverable. Each carries a type label (research, prototype, grilling, or task) and is sized to fit one 100K-token agent session.
It works with any tracker that supports child issues, labels, assignment, and native blocking relationships; the tracker-specific operations live in a separate tracker doc. If no tracker is provided, it 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 is the set of open, unblocked, unclaimed tickets, and each session resolves at most one ticket, except research tickets.
Skip the map when charting surfaces no fog: if the way to the destination is already clear and the whole journey fits in one session, a map adds overhead. The skill itself stops and asks how to proceed in that case.
AnasIsmai1Decomposes vague ideas into tracked investigation tickets on an issue tracker.
JhonMA82Executes written implementation plans task-by-task with review checkpoints and verification steps.
The-Vibe-CompanyPlan large efforts as decision tickets on an issue tracker and resolve them incrementally.
telefrekImplement small code changes with TDD and minimal setup.