Plans large efforts as decision-ticket maps on an issue tracker.
npx skills add https://github.com/AO-HyS/aohys.com --skill wayfinder-ao-hys
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/wayfinder Command: npx skills add https://github.com/AO-HyS/aohys.com --skill wayfinder-ao-hys
wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope boundaries. - Typed decision tickets: Breaks work into child issues typed as research, prototype, grilling, or task, with HITL/AFK modes, native blocking relationships, and claim-by-assignment for concurrent sessions. - Progressive refinement: Graduates vaguely understood 'fog' into sharp tickets as the frontier advances, and closes mis-scoped tickets into an explicit out-of-scope record. - Use Case: A team facing a vague migration or spec effort invokes the skill to chart a map, then works one decision ticket per session—research subagents run in parallel—until every decision needed before execution is resolved. ## Quick Start Ask the agent to use the wayfinder skill to chart a map for your loosely defined effort, naming the destination you want to reach.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, sketches unresolved fog, and creates decision tickets as child issues on your issue tracker. Each later session claims and resolves one ticket until the way is clear.
A decision ticket is a child issue whose resolution is a decision rather than a build slice. It carries a type label—research, prototype, grilling, or task—and is sized to fit one agent session, with the answer recorded as a resolution comment on close.
The map and tickets live on whatever issue tracker the repo provides, using its native labels, child issues, and blocking relationships. If no tracker is configured, it falls back to a local-markdown tracker and asks you to run the setup command.
Yes. A session claims a ticket by assigning it before starting work, so concurrent sessions skip claimed tickets. Research tickets can also be resolved in parallel by subagents on throwaway branches.
Skip the map when charting surfaces no fog—when the path to the destination is already clear and the whole effort fits in one session. The skill is for planning decisions, not executing deliverables.
ArcReelPlan large efforts as decision tickets tracked on an issue tracker.
w5851Synthesize literature evidence into engineering recommendations and implementation plans.
haryelramalhoInterrogate plans and designs to produce decision records and a glossary.
sumitakePlans multi-session efforts as decision tickets on the repository issue tracker.