arda/skills
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rename the two buckets to plain map headings: Not yet specified / Out of scope

Browse source 
Following review: the map-body headings a cold reader sees should be
self-evident without having read the skill, so drop the metaphor from
the headings — `## Not yet specified` (in-scope, unripe) and
`## Out of scope` (beyond the destination). Keep **fog of war** as the
leading word: it still titles the explanatory section and drives the
"clears the fog" / "graduate the fog" behavior in the prose.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock 2026-07-05 17:35:50 +01:00
parent 299eb0c017
commit 3ea01314c1
2 changed files with 19 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

6
.changeset/wayfinder-deferred-section.md
View file

@ -2,6 +2,8 @@
"mattpocock-skills": minor
---
Give **`wayfinder`** a distinct **`## Deferred`** section for work that lies _beyond_ the destination, separating it from Fog.
Split **`wayfinder`**'s map-body catch-all into two plainly-named sections — **`## Not yet specified`** and **`## Out of scope`** — so a cold reader can tell in-scope-but-unripe work from work ruled beyond the destination.
Fog is the undiscovered frontier _toward_ the destination — in scope, just not yet sharp — so it graduates into tickets as the frontier advances. Work ruled out of _this_ effort's scope was being parked in Fog too, where it read as takeable frontier. It now has its own home: the `## Deferred` section, which never graduates (the frontier stops at the destination) and returns only as a fresh effort if the destination is redrawn. The "Fog or ticket?" test becomes "Fog, ticket, or deferred?" — gated on scope as well as sharpness — and both charting and working-the-map now defer a ticket found beyond the destination (close it, record one line in Deferred) rather than leaving it on the frontier or logging it in Decisions so far.
Previously both lived under one `## Fog` heading, where out-of-scope work read as takeable frontier (an unblocked, unclaimed item is indistinguishable from a live ticket). Now: *Not yet specified* is the in-scope frontier that graduates into tickets as decisions resolve; *Out of scope* is beyond the destination, closed and never graduating, returning only as a fresh effort if the destination is redrawn. The "Fog or ticket?" test becomes "Ticket, not-yet-specified, or out of scope?", gated on scope as well as sharpness, and both charting and working-the-map now rule a beyond-destination ticket out of scope (close it, one line in *Out of scope*) rather than leaving it on the frontier or logging it in *Decisions so far*.
The **fog of war** leading word is retained — it still names the concept and drives the graduate-the-fog behavior in the skill's prose; only the human-facing map headings go to plain language.