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

Split charting triage into two grilling steps: destination, then frontier

Browse source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock 2026-07-05 15:02:39 +01:00
parent c808f64f92
commit 913a105881
1 changed files with 5 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -89,10 +89,11 @@ Two modes. Either way, **never resolve more than one ticket per session.**
User invokes with a loose idea.
1. **Name the destination, then map the frontier.** Run a **breadth-first** `/grilling` and `/domain-modeling` session: first pin down what this map is finding its way to — the spec, decision, or change — then fan out across the whole space rather than deep on any one thread, surfacing the open decisions and the first steps takeable now. The destination fixes the scope; the breadth-first pass finds the frontier. Both are settled before any ticket exists.
2. **Create the map** (label `wayfinder:map`): Destination and 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.
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.
3. **Create the map** (label `wayfinder:map`): Destination and Notes filled in, Decisions-so-far empty, Fog sketched.
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.
5. Stop — charting the map is one session's work; do not also resolve tickets.
### Work through the map