--- id: gh-wayfinder name: "wayfinder" url: https://skills.yangsir.net/skill/gh-wayfinder author: mattpocock domain: ai-project-management-collaboration tags: ["problem-solving", "task-management", "project-planning", "workflow", "investigation"] install_count: 710600 rating: 4.90 (120 reviews) github: https://github.com/mattpocock/skills/tree/main/skills/in-progress/wayfinder --- # wayfinder > 此技能帮助用户将模糊不清的复杂问题转化为结构化的调查任务地图，并逐一解决，直至目标明确。它通过创建可追踪的“票据”来分解问题，明确依赖关系，并指导用户系统性地推进，从而将不确定的想法转化为清晰可行的计划。 **Stats**: 710,600 installs · 4.9/5 (120 reviews) ## Before / After 对比 ### 复杂问题澄清效率 **Before**: 用户/开发者在面对模糊不清的复杂问题时，往往难以找到明确的切入点和解决路径，导致长时间的摸索和低效的讨论。 **After**: 该 Skill 能够将复杂问题分解为一系列清晰的调查任务，明确依赖关系，使用户/开发者能够系统性地推进，显著提升问题澄清的效率。 | Metric | Before | After | Change | |---|---|---|---| | 决策点模糊度 | 80% | 15% | -81% | ## Readme A loose idea has arrived — too big for one agent session, and wrapped in fog: the route from here to a plan isn't visible yet. This skill charts it: stand up a map, then work its tickets one at a time until the way to the goal is clear. The map is domain-agnostic — engineering work, course content, whatever fits the shape. ## The Map The map is a single compact Markdown file, one per wayfinding effort, git-tracked alongside the project. It is the canonical artifact — the **whole map is loaded as context into every session**, so it must stay compact. Assets created during tickets should be linked to from the map, not duplicated within it. ### Structure Entries ("tickets"), each its own section keyed by a short dash-case slug that reads as a mini-title (e.g. `relational-db`, `auth-strategy`, `cache-layer`) — terse enough to stay token-efficient, and unique within the map. ```markdown ## relational-db: Relational Or Non-Relational Database? Blocked by: , Status: open | in-progress | resolved Type: Research | Prototype | Grilling | Task ### Question ### Answer ``` The slug is the canonical id, used in every `Blocked by` edge and prose reference; the title after the colon is optional. A ticket is **unblocked** when every ticket in its `Blocked by` list is `resolved`. A session **claims** its ticket by setting `Status: in-progress` and saving the map before any work, so concurrent sessions skip it. Each ticket must be sized to one 100K token agent session. ## Ticket Types There are four types of tickets: - **Research**: Reading documentation, third-party API's, or local resources like knowledge bases. Creates a markdown summary as an asset. Use this when knowledge outside the current working directory is required. - **Prototype**: Raise the fidelity of the discussion by making a cheap, rough, concrete artifact to react to — an outline, a rough take, a stub, or UI/logic code via the /prototype skill. Creates the prototype as an asset. Use this when "how should it look" or "how should it behave" is the key question. - **Grilling**: Conversation with the agent. Uses the /grilling and /domain-modeling skills. Asks one question at a time. The default case. - **Task**: Literal manual work that must be done before the discussion can move forward — nothing to decide, prototype, or research. Moving data from one place to another, signing up for a third-party service, provisioning access. The agent automates it where it can; otherwise it hands the human a precise checklist to do by hand. Resolved when the work is done; the answer records what was done and any resulting facts (credentials location, new URLs, row counts) later tickets depend on. ## Fog of war The map is _deliberately_ incomplete beyond the frontier — don't chart what you can't yet see. The frontier is the unblocked tickets at the edge of the known; resolve them to push it forward. Push back the fog of war one ticket at a time, until the way to the goal is clear and no tickets remain. ## Invocation Two branches. Either way, **every session ends with a [Handoff](#handoff)** — never resolve more than one ticket per session. ### Chart the map User invokes with a loose idea. 1. Run a `/grilling` and `/domain-modeling` session to surface the open decisions. 2. Write a new map — mostly fog, frontier identified, trivially-decidable entries resolved inline. 3. Handoff. Charting the map is one session's work; do not also resolve tickets. ### Work through the map User invokes with a path to an existing map. A ticket slug is **optional** — without one, you pick the next decision, not the user. 1. Load the **whole map** as context. 2. Choose the ticket. If the user named one, use it. Otherwise pick the first `open` ticket in document order that is [unblocked](#structure). [Claim it](#structure): set `Status: in-progress` and save before any work. 3. Resolve it, invoking skills as needed — including any the `## Notes` block names. If in doubt, use `/grilling` and `/domain-modeling`. 4. Record the answer in the ticket's body and set `Status: resolved`. 5. Add newly-discovered tickets with correct `Blocked by` edges. If the decisions made invalidate other parts of the map, update or delete those tickets. 6. Handoff. The user may run unblocked tickets in parallel, so expect other agents to be editing the map in their own sessions. ## Handoff End every session by clearing the context and opening one or more fresh sessions. Close with a **Next steps** block the user can copy-paste. Two cases: **Open tickets remain.** List the currently-unblocked tickets, then give two copy-paste options: a bare command for one session (you pick the next ticket), and one pinned command per unblocked ticket for running them in parallel. Paste one line per fresh window — opening one, some, or all of them. > **Next steps** — 3 tickets unblocked: `auth-strategy`, `cache-layer`, `rate-limits`. > Clear the context, then open fresh sessions. > > **One session** — resolves the next unblocked ticket: > ``` > Invoke /wayfinder with the map at . > ``` > > **Parallel** — paste one line per window, up to all 3: > ``` > Invoke /wayfinder with the map at , ticket auth-strategy. > Invoke /wayfinder with the map at , ticket cache-layer. > Invoke /wayfinder with the map at , ticket rate-limits. > ``` **No open tickets remain.** The fog is pushed back far enough that the way to the goal is clear — the map is done. (The initial grilling may also surface no fog at all, in which case there was never a map to chart.) Recommend implementing directly, or using `/to-prd` to schedule a multi-session implementation. ## Notes An optional block declaring the **domain**, any skills every session should `consult`, and freeform standing preferences for this effort. --- *Source: https://skills.yangsir.net/skill/gh-wayfinder* *Markdown mirror: https://skills.yangsir.net/api/skill/gh-wayfinder/markdown*