wayfinder: recheck claims before showing the frontier in Handoff

Add a gate at the top of the Handoff section that rereads the session's
assertions — the resolution answer, the appended Decisions-so-far line,
and facts later tickets depend on — against the actual tracker state and
linked assets, fixing whatever doesn't hold, before the Next steps block
reveals the available sessions and new frontier.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

.changeset/wayfinder-plan-big-work.md

@@ -1,7 +0,0 @@
----
-"mattpocock-skills": minor
----
-
-Reframe **`wayfinder`**'s description around the work it's for: planning a huge chunk of work, more than one agent session can hold.
-
-The description does the skill's invocation work, so it now leads with the trigger that actually reaches for Wayfinder — a big effort you need to break down — instead of the softer "chart a route through a foggy problem". The skill body and fog-of-war mechanic are unchanged.

skills/in-progress/wayfinder/SKILL.md

@@ -1,13 +1,13 @@
 ---
 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 goal is clear.
+description: Chart a route through a foggy problem — turn a loose idea into a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the goal is clear.
 ---
 
 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 as a **shared map** on the repo's issue tracker, then works its tickets one at a time. The map is domain-agnostic — engineering work, course content, whatever fits the shape.
 
 ## Refer by name
 
-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.
+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, the Handoff — 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, and Handoff commands still paste the URL — but they ride *inside* the name, never stand in for it.
 
 ## The Map
 
@@ -78,7 +78,7 @@ Fog excludes only what's already decided (that's Decisions so far) and what's al
 
 ## Invocation
 
-Two modes. Either way, **never resolve more than one ticket per session.**
+Two modes. Either way, **every session ends with a [Handoff](#handoff)** — never resolve more than one ticket per session.
 
 ### Chart the map
 
@@ -87,7 +87,7 @@ User invokes with a loose idea.
 1. Run a `/grilling` and `/domain-modeling` session to surface the open decisions.
 2. **Create the map** (label `wayfinder:map`): Notes filled in, Decisions-so-far empty, Fog sketched.
 3. **Create the tickets you can specify now** as child issues of the map — then wire blocking edges in a **second pass** (issues need ids before they can reference each other). Wiring sorts them into the frontier and the blocked; everything you can't yet specify stays in the Fog.
-4. Stop — charting the map is one session's work; do not also resolve tickets.
+4. Handoff. Charting the map is one session's work; do not also resolve tickets.
 
 ### Work through the map
 
@@ -98,5 +98,32 @@ User invokes with a map (URL or number). A ticket is **optional** — without on
 3. Resolve it — **zoom as needed**: fetch the full body of any related or closed ticket on demand; invoke the skills the `## Notes` block names. If in doubt, use `/grilling` and `/domain-modeling`.
 4. Record the resolution: post the answer as a **resolution comment**, **close** the issue, and **append a context pointer** to the map's Decisions-so-far.
 5. Add newly-surfaced tickets (create-then-wire); graduate any fog the answer has made specifiable, clearing each graduated patch from the Fog so it lives only as its new ticket. If the decision invalidates other parts of the map, update or delete those tickets.
+6. Handoff.
 
 The user may run unblocked tickets in parallel, so expect other sessions to be editing the tracker concurrently.
+
+## Handoff
+
+**Recheck your claims first.** Before you show the frontier, reread every assertion you're about to hand off — the resolution answer, the Decisions-so-far line you appended, any facts later tickets will depend on — against the actual tracker state and the assets you linked, and fix whatever doesn't hold. The available sessions and the new frontier the human is about to act on are only as sound as the claims underneath them.
+
+Then end every session with a **Next steps** block the user can copy-paste. Two cases:
+
+**Open tickets remain.** Query the map for the currently-unblocked children, 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** — *<map name>*: 3 tickets unblocked. Clear the context, then open fresh sessions.
+>
+> **One session** — resolves the next unblocked ticket:
+>
+> ```
+> Invoke /wayfinder with the map <map-url>.
+> ```
+>
+> **Parallel** — paste one line per window, up to all 3:
+>
+> ```
+> Invoke /wayfinder with the map <map-url>, ticket <issue-url>.  # <ticket name>
+> Invoke /wayfinder with the map <map-url>, ticket <issue-url>.  # <ticket name>
+> Invoke /wayfinder with the map <map-url>, ticket <issue-url>.  # <ticket name>
+> ```
+
+**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.