Plan large efforts as decision tickets on an issue tracker and resolve them incrementally.
npx skills add https://github.com/taxmaxi/taxmaxi --skill wayfinder-taxmaxi
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/taxmaxi/taxmaxi/tree/main/.agents/skills/wayfinder Command: npx skills add https://github.com/taxmaxi/taxmaxi --skill wayfinder-taxmaxi
wayfinder:map) holding the destination, notes, decisions-so-far index, fog of war, and out-of-scope boundaries. - Typed decision tickets: Splits work into research, prototype, grilling, and task tickets, each sized to one agent session, with native blocking relationships defining the 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 have a vague migration idea too big for one session. Invoke Wayfinder to grill out the destination, fan out the open decisions into tickets, fire research subagents in parallel, and then resolve tickets session by session until the route is clear. ## 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 Wayfinder with your loose idea. It grills you to name the destination, maps the open decisions breadth-first, creates a map issue plus typed tickets on the issue tracker, and wires blocking edges so each later session resolves one ticket at a time.
A decision ticket is a child issue of the map whose body states one question sized to a single 100K-token session. Each carries a type label: research, prototype, grilling, or task, and is resolved by posting a resolution comment and closing the issue.
Wayfinder is tracker-agnostic but needs labels, child issues, assignees, and ideally native blocking relationships. The tracker-specific operations live in a tracker doc; if none 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. Research tickets are the exception to the one-ticket-per-session rule and can be fanned out to parallel subagents.
Skip it when the way to the destination is already clear and the whole effort fits in one session; charting would add overhead with no fog to clear. It also produces decisions, not deliverables, unless the map's Notes explicitly carry execution into the map.
petemcwPlan large work efforts as decision-ticket maps on an issue tracker.
iusztinpaulCoordinate software-engineer and tester agents to implement and commit a single ticket.
amazingloft999-droidInterrogate product plans against the domain model and update CONTEXT.md and ADRs.
rogerzntsPlans large multi-session efforts as decision-ticket maps on an issue tracker.