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

wayfinder: prefer native blocking, and say why

Browse source 
The blocking rule now leads with the tracker's native dependency
relationship and encodes the rationale: native rendering makes the
frontier visible in the tracker's own UI, so the human sees what's
takeable without opening the map. Notes the body-convention fallback
for trackers that lack native blocking (GitHub has it; GitLab only on
paid tiers).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock 2026-07-03 10:39:04 +01:00
parent e9dea692fd
commit b289481499
2 changed files with 8 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

7
.changeset/wayfinder-native-blocking-rationale.md Normal file
View file

@ -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.

2
skills/in-progress/wayfinder/SKILL.md
View file

@ -52,7 +52,7 @@ Two label families:
- `wayfinder:<type>` — 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.