| name | wayfinder |
| description | Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear. |
| 触发词 | 将超一个会话容量的大块工作规划为共享调查 ticket 地图，逐个解决直到通往目的地的路径清晰。 |
| disable-model-invocation | true |
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the destination isn't visible yet. Wayfinding is about finding that way, not charging at the destination. This skill charts the way as a shared map on the repo's issue tracker, then works its tickets one at a time until the route is clear.
一个松散的想法已经到来——超出单个 Agent 会话的容量，且包裹在迷雾之中：从这里到目的地的路径尚不可见。寻路（wayfinding）是关于找到那条路，而非冲向目的地。该技能在仓库的 issue 跟踪器上将路径描绘为一张共享地图，然后逐个处理 ticket，直到路线清晰为止。
The destination varies per effort, and naming it is the first act of charting — it shapes every ticket. It might be a spec to hand off and iterate on, a decision to lock before planning starts, or a change made in place like a data-structure migration. The map is domain-agnostic — engineering work, course content, whatever fits the shape.
目的地因工作而异，命名它是绘制地图的第一步——它塑造了每个 ticket。它可能是一份待交接和迭代的规格说明、一个在规划开始前就需要锁定的决策、或一个就地完成的变更（如数据结构迁移）。地图是领域无关的——工程工作、课程内容，任何符合其形态的事物。
Wayfinder is planning by default: each ticket resolves a decision, and the map is done when the way is clear — nothing left to decide before someone goes and does the thing. The pull to just do the work is usually the signal you've reached the edge of the map and it's time to hand off. An effort can override this in its Notes — carrying execution into the map itself — but absent that, produce decisions, not deliverables.
Wayfinder 默认是规划：每个 ticket 解决一个决策，地图在路线清晰时完成——在有人去执行之前没有需要决定的遗留事项。那种只想直接开干的冲动，通常是你已到达地图边缘、可以交接的信号。一项工作可以在其 Notes 中覆盖此规则——将执行带入地图本身——但若无此声明，产出的是决策，而非交付物。
Every map and ticket is an issue, so it has a name — its title. In everything the human reads — narration, the map's Decisions-so-far — refer to it by that name, never by a bare id, number, or slug. A wall of #42, #43, #44 is illegible; names read at a glance. The id and URL don't vanish — a name wraps its link — but they ride inside the name, never stand in for it.
每个地图和 ticket 都是一个 issue，因此它有一个名称——它的标题。在人类阅读的所有内容中——叙述、地图的「已作决策」——都以该名称引用，绝不使用裸 ID、编号或短链接。满眼的 #42, #43, #44 难以辨认；名称则一目了然。ID 和 URL 并未消失——名称包裹着它的链接——但它们承载在名称之内，绝不取而代之。
The map is a single issue on this repo's issue tracker, labelled wayfinder:map — the canonical artifact. Its tickets are child issues of the map.
地图是本仓库 issue 跟踪器上的一个 issue，标有 wayfinder:map 标签——它是规范制品。其 ticket 是地图的子 issue。
The map is an index, not a store. It lists the decisions made and points at the tickets that hold their detail; a decision lives in exactly one place — its ticket — so the map never restates it, only gists it and links.
地图是一个索引，而非仓库。它列出已作决策并指向持有其细节的 ticket；一个决策只存在于一个地方——它的 ticket——因此地图从不复述，只做摘要和链接。
Where the map, its child tickets, blocking, and frontier queries physically live is tracker-specific. The issue tracker should have been provided to you — run /setup-matt-pocock-skills if not. Consult the tracker doc's "Wayfinding operations" section for how this repo expresses them. If no tracker has been provided, default to the local-markdown tracker.
地图、其子 ticket、阻塞关系和前沿查询的物理存储方式因跟踪器而异。 你应该已配备 issue 跟踪器——如果没有，运行 /setup-matt-pocock-skills。查阅跟踪器文档的「Wayfinding 操作」章节，了解本仓库如何表达它们。如果未提供跟踪器，默认使用本地 markdown 跟踪器。
The whole map at low resolution, loaded once per session. Open tickets are not listed — they are open child issues, found by query.
整个地图以低分辨率呈现，每个会话加载一次。开放的 ticket 不列出——它们是开放的子 issue，通过查询获取。
## Destination
<what reaching the end of this map looks like — the spec, decision, or change this effort is finding its way to. One or two lines; every session orients to it before choosing a ticket.>
## Notes
<domain; skills every session should consult; standing preferences for this effort>
## Decisions so far
<!-- the index — one line per closed ticket: enough to judge relevance, then zoom the link for the detail the ticket holds -->
- [<closed ticket title>](link) — <one-line gist of the answer>
## Not yet specified
<!-- see "Fog of war": in-scope fog you can't ticket yet; graduates as the frontier advances -->
## Out of scope
<!-- see "Out of scope": work ruled beyond the destination; closed, never graduates -->## 目的地（Destination）
<到达此地图终点时是什么样的——本工作正在寻找路径的规格说明、决策或变更。一行或两行；每个会话在选择 ticket 之前以其为方向。>
## 备注（Notes）
<领域；每个会话应查阅的技能；本工作的常设偏好>
## 已作决策（Decisions so far）
<!-- 索引——每个已关闭 ticket 一行：足以判断相关性，然后通过链接放大查看 ticket 持有的细节 -->
- [<已关闭 ticket 标题>](link) — <单行答案摘要>
## 尚未明确（Not yet specified）
<!-- 见「战争迷雾」：范围内尚不可成 ticket 的迷雾；随着前沿推进而转化 -->
## 超出范围（Out of scope）
<!-- 见「超出范围」：被裁定超出目的地的工作；已关闭，永不转化 -->Each ticket is a child issue of the map; the tracker's issue id is its identity. Its body is the question, sized to one 100K token agent session:
每个 ticket 是地图的一个子 issue；跟踪器的 issue ID 是其标识。其正文是问题本身，大小限定在一个 100K token 的 Agent 会话内：
## Question
<the decision or investigation this ticket resolves>## 问题（Question）
<此 ticket 要解决的决策或调研事项>Each ticket carries a wayfinder:<type> label — one of research, prototype, grilling, task (see Ticket Types).
每个 ticket 带有一个 wayfinder:<type> 标签—— research、prototype、grilling 或 task 之一（见票种类型）。
A session claims a ticket by assigning it to the dev driving the map, first, before any work, so concurrent sessions skip it. That assignee is the claim: an open, unassigned ticket is unclaimed.
会话通过将 ticket 指派给推动地图的开发人员来认领，首先执行，在工作之前，以便并发的会话跳过它。该指派人就是认领：一个开放、未指派的 ticket 就是未认领的。
Blocking uses the tracker's native dependency relationship — essential because it renders the frontier visually in the tracker's own UI, so the human sees what's takeable without opening the map. Only a tracker that lacks native blocking falls back to a body convention. A ticket is unblocked when every ticket blocking it is closed; the frontier is the open, unblocked, unclaimed children — the edge of the known.
阻塞关系使用跟踪器的原生依赖关系——这很关键，因为它能在跟踪器自身的 UI 中可视化地呈现前沿，让人无需打开地图就能看到哪些 ticket 可接手。只有缺乏原生阻塞功能的跟踪器才会回退到正文约定。当阻塞它的所有 ticket 都已关闭时，该 ticket 即为未阻塞；前沿是开放、未阻塞、未认领的子 ticket——已知的边缘。
The answer isn't part of the body — it's recorded on resolution (see Work through the map). Assets created while resolving a ticket are linked from the issue, not pasted in.
答案不是正文的一部分——它在解决时记录（见推进地图）。解决 ticket 过程中创建的资产通过链接关联到 issue 中，而非粘贴进去。
Every ticket is either HITL — human in the loop, worked with a human who speaks for themselves — or AFK, driven by the agent alone. A HITL ticket only resolves through that live exchange; the agent never stands in for the human's side of it (a grilling agent that answers its own questions has broken this).
每个 ticket 要么是 HITL——人在循环中，与有自主表达能力的人一起工作——要么是 AFK，由 Agent 单独推动。HITL ticket 只能通过实时交流解决；Agent 永远不能替代人类的立场（一个自己回答自己问题的 grilling Agent 就已经打破了这一规则）。
/prototype skill. Links the prototype as an asset. Use when "how should it look" or "how should it behave" is the key question./grilling and /domain-modeling skills, one question at a time. The default case./prototype 技能创建的 UI/逻辑代码。将原型链接为资产。当「它应该长什么样」或「它应该如何行为」是关键问题时使用。/grilling 和 /domain-modeling 技能进行的对话，一次一个问题。默认情况。The map is deliberately incomplete: don't chart what you can't yet see. Beyond the live tickets lies the fog of war — the dim view of decisions and investigations you can tell are coming but can't yet pin down, because they hang on questions still open. Resolving a ticket clears the fog ahead of it, graduating whatever's now specifiable into fresh tickets — one at a time, until the way to the destination is clear and no tickets remain.
地图是刻意不完整的：不要绘制你还看不见的东西。在活跃 ticket 之外是战争迷雾——你能感到即将到来但尚无法确定下来的决策和调研的模糊视图，因为它们依赖尚未解决的问题。解决一个 ticket 会清除其前方的迷雾，将现在可明确的事项转化（graduate）为新的 ticket——一次一个，直到通往目的地的路径清晰且不再有 ticket 残留。
The map's Not yet specified section is where that dim view is written down: the suspected question, the area to revisit later. It's the undiscovered frontier toward the destination — everything here is in scope, just not sharp enough to ticket. Write as loosely or as fully as the view allows; it doubles as a signpost for collaborators reading where the effort is headed.
地图的「尚未明确」部分就是写下那个模糊视图的地方：存疑的问题，稍后需重新审视的区域。它是通往目的地途中尚未发现的前沿——这里的一切都在范围内，只是还不够清晰到可以创建 ticket。根据视图允许的程度写得松散或完整均可；它同时也为阅读此工作的协作者指明方向。
Fog or ticket? The test is whether you can state the question precisely now — not whether you can answer it now.
迷雾还是 ticket？ 判断标准是现在能否精确陈述问题——而非现在能否回答它。
Not yet specified excludes what's already decided (Decisions so far), what's already a live ticket, and what's out of scope (the next section).
「尚未明确」排除了已经决定的内容（已作决策）、已经是活跃 ticket 的内容以及超出范围的内容（下一节）。
Fog only ever gathers toward the destination. The destination fixes the scope, so work beyond it is out of scope — it isn't fog, and it doesn't belong in Not yet specified. It gets its own Out of scope section on the map: work you've consciously ruled out of this effort. Scope, not sharpness, lands it here.
迷雾只存在于朝向目的地的方向上。目的地固定了范围，因此超出目的地的工作是超出范围的——它不是迷雾，也不属于「尚未明确」。它在地图上有自己的「超出范围」部分：你自觉排除出本工作的工作。是范围，而非清晰度，将其归入此处。
Out-of-scope work never graduates — the frontier stops at the destination — so it returns only if the destination is redrawn, and then as a fresh effort, not a resumption.
超出范围的工作永远不会转化——前沿止步于目的地——因此它只有在目的地被重新绘制时才会回归，而且是以新的工作而非恢复。
Ruling something out of scope is a scoping act, not a step on the route. When a ticket that already exists turns out to sit past the destination — mis-scoped in while charting, or exposed by a resolution — close it (a closed ticket is unambiguously off the frontier) and leave one line in the Out of scope section: the gist plus why it's out of scope, linking the closed ticket. It stays out of Decisions so far, which records the route actually walked — a scope boundary isn't a step on it.
将某事物裁定为超出范围是一个范围界定行为，而非路线上的一个步骤。当已经存在的 ticket 被发现位于目的地之外时——在绘制地图时错误纳入，或通过解决暴露——关闭它（已关闭的 ticket 明确地不在前沿上），并在「超出范围」部分留下一行：要点加为什么超出范围，链接到已关闭的 ticket。它不进入「已作决策」，后者记录的是实际走过的路线——范围边界不是路线上的一个步骤。
Two modes. Either way, never resolve more than one ticket per session.
两种模式。无论哪种，每个会话绝不解决超过一个 ticket。
User invokes with a loose idea.
用户带着一个松散想法调用。
/grilling and /domain-modeling session to pin down what this map is finding its way to — the spec, decision, or change. The destination fixes the scope, so it's settled first.wayfinder:map): Destination and Notes filled in, Decisions-so-far empty, the fog sketched into Not yet specified./grilling 和 /domain-modeling 会话，确定此地图正在寻找路径的目标——规格说明、决策或变更。目的地固定了范围，因此首先解决它。wayfinder:map）：填写目的地和备注，已作决策为空，将迷雾勾勒到「尚未明确」中。User invokes with a map (URL or number). A ticket is optional — without one, you pick the next decision, not the user.
用户带地图（URL 或编号）调用。ticket 是可选的——如果没有指定，你选择下一个决策，而非用户。
## Notes block names. If in doubt, use /grilling and /domain-modeling.## Notes 块中命名的技能。如有疑问，使用 /grilling 和 /domain-modeling。The user may run unblocked tickets in parallel, so expect other sessions to be editing the tracker concurrently.
用户可能并行运行未阻塞的 ticket，因此预期其他会话可能同时编辑跟踪器。