From 55511cea24e163655a8cb7f9e463acb0913b7fdc Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Mon, 6 Jul 2026 13:36:44 +0100 Subject: [PATCH] wayfinder: restore no-fog early exit Bring back the "skip the map when there's no fog" branch that was collateral-deleted with the Handoff section. Co-located in Chart the map step 2, where the fog/no-fog outcome is determined: if breadth-first grilling surfaces no fog, offer to skip the map and implement directly. The offer (ask, don't auto-skip) is preserved from the original. Co-Authored-By: Claude Opus 4.8 (1M context) --- .changeset/wayfinder-no-fog-early-exit.md | 9 +++++++++ skills/in-progress/wayfinder/SKILL.md | 2 +- 2 files changed, 10 insertions(+), 1 deletion(-) create mode 100644 .changeset/wayfinder-no-fog-early-exit.md diff --git a/.changeset/wayfinder-no-fog-early-exit.md b/.changeset/wayfinder-no-fog-early-exit.md new file mode 100644 index 0000000..aa881c7 --- /dev/null +++ b/.changeset/wayfinder-no-fog-early-exit.md @@ -0,0 +1,9 @@ +--- +"mattpocock-skills": patch +--- + +Restore **`wayfinder`**'s early exit when the frontier grilling turns up no fog. + +The skill used to have a **Skipping The Decision Map** section: if the opening grilling surfaced no fog of war, there was no map to build, so it offered to skip straight to implementing. That clause was demoted to a parenthetical inside the Handoff section, then deleted as collateral when Handoff was removed — never an intentional cut. + +It's back, co-located in **Chart the map** step 2 (Map the frontier), where the fog/no-fog outcome is actually determined: if breadth-first grilling surfaces no fog, tell the user and offer to skip the map, implementing directly instead. The offer — asking rather than auto-skipping — is preserved from the original. diff --git a/skills/in-progress/wayfinder/SKILL.md b/skills/in-progress/wayfinder/SKILL.md index 0c5e652..a76d018 100644 --- a/skills/in-progress/wayfinder/SKILL.md +++ b/skills/in-progress/wayfinder/SKILL.md @@ -102,7 +102,7 @@ Two modes. Either way, **never resolve more than one ticket per session.** User invokes with a loose idea. 1. **Name the destination.** Run a `/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. -2. **Map the frontier.** Grill again, **breadth-first** this time: fan out across the whole space rather than deep on any one thread, surfacing the open decisions and the first steps takeable now. +2. **Map the frontier.** Grill again, **breadth-first** this time: fan out across the whole space rather than deep on any one thread, surfacing the open decisions and the first steps takeable now. **If this surfaces no fog** — every decision already takeable, the way to the destination clear — there's nothing to chart: tell the user and offer to skip the map, implementing directly instead. 3. **Create the map** (label `wayfinder:map`): Destination and Notes filled in, Decisions-so-far empty, the fog sketched into **Not yet specified**. 4. **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 — the **Not yet specified** section. 5. Stop — charting the map is one session's work; do not also resolve tickets.