Plans large efforts as decision-ticket maps on an issue tracker.
npx skills add https://github.com/wenyue/SmartKit --skill wayfinder-wenyue
Please help me install this Agent Skill. Skill: wayfinder Source: https://github.com/wenyue/SmartKit/tree/main/skills/wayfinder Command: npx skills add https://github.com/wenyue/SmartKit --skill wayfinder-wenyue
wayfinder:map) holding the destination, notes, decisions-so-far index, fog-of-war items, and out-of-scope rulings. - Typed decision tickets: Breaks work into child issues typed as research, prototype, grilling, or task, with native blocking relationships defining the actionable frontier. - Concurrent session safety: Claims tickets via assignment, limits resolution to one ticket per session, and supports parallel research subagents. - Use Case: A team facing a vague data-structure migration invokes the Skill to chart a map, grill the destination, spawn research subagents on open questions, and work tickets session by session until every decision is resolved. ## Quick Start Ask the agent to chart a wayfinder map for your loosely defined initiative so it can create the destination, tickets, and blocking edges on your issue tracker.High-intent search queries and answers about installing and using this skill.
Invoke the wayfinder skill with your loose idea. It runs a grilling session to name the destination, maps the frontier breadth-first, creates a map issue with child decision tickets, and wires blocking edges so future sessions resolve one ticket at a time.
A decision ticket is a child issue of the map whose resolution is a decision rather than a build slice. Each carries a type label — research, prototype, grilling, or task — and is sized to fit one 100K-token agent session.
Wayfinder is tracker-agnostic but expects a tracker doc describing how the repo expresses maps, child tickets, blocking, and frontier queries. If no tracker is provided, it defaults to a local-markdown tracker; trackers without native blocking fall back to a body convention.
Yes. Sessions claim tickets by assigning them before starting work, so concurrent sessions skip claimed items. Research tickets can also be resolved in parallel by dedicated research subagents on throwaway branches.
Skip it when the way to the destination is already clear and the whole effort fits in one session — charting surfaces no fog in that case. It is also planning-only by default, producing decisions rather than deliverables unless the map's Notes override this.
shushuznConfigure engineering-skills context with issue tracker and triage label settings.
xriuPlans large efforts as decision tickets on an issue tracker and resolves them one at a time.
amazingloft999-droidInterrogate product plans against the domain model and update CONTEXT.md and ADRs.
telefrekImplement small code changes with TDD and minimal setup.