diff --git a/.changeset/wayfinder-native-blocking-rationale.md b/.changeset/wayfinder-native-blocking-rationale.md new file mode 100644 index 0000000..6d73798 --- /dev/null +++ b/.changeset/wayfinder-native-blocking-rationale.md @@ -0,0 +1,7 @@ +--- +"mattpocock-skills": patch +--- + +Sharpen **`wayfinder`**'s blocking rule to prefer the tracker's native dependency relationship and say why. + +Native blocking is essential rather than cosmetic: it renders the frontier visually in the tracker's own UI, so the human sees what's takeable at a glance without opening the map. The rule now states that preference explicitly, notes the body-convention fallback for trackers that lack native blocking, and ties the frontier to what the human picks from. diff --git a/skills/in-progress/wayfinder/SKILL.md b/skills/in-progress/wayfinder/SKILL.md index 8cb6b23..b86c59e 100644 --- a/skills/in-progress/wayfinder/SKILL.md +++ b/skills/in-progress/wayfinder/SKILL.md @@ -52,7 +52,7 @@ Two label families: - `wayfinder:` — one of `research`, `prototype`, `grilling`, `task` (see [Ticket Types](#ticket-types)). - `wayfinder:claimed` — a session sets this **first**, before any work, so concurrent sessions skip it. -Blocking uses the tracker's native semantics. A ticket is **unblocked** when every ticket blocking it is closed. The **frontier** is the open, unblocked, unclaimed children — the edge of the known. +Blocking uses the tracker's **native** dependency relationship wherever the tracker has one. Native is essential, not cosmetic: it renders the frontier _visually_ in the tracker's own UI, so the human sees what's takeable at a glance without opening the map. Only where a tracker has no native blocking does the mechanics fall 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, and what the human picks from. The answer isn't part of the body — it's recorded on resolution (see [Work through the map](#work-through-the-map)). Assets created while resolving a ticket are linked from the issue, not pasted in.