wayfinder

Name: wayfinder
Author: tt-a1i

16stars3forks

How to install wayfinder?

tt-a1i/matt-skills-with-to-goal/wayfinder

$npx -y skills add tt-a1i/matt-skills-with-to-goal --skill wayfinder

Installs into the current project.

Summary

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Files · 1

View on GitHub

SKILL.md

1	A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the destination isn't visible yet. Wayfinding is about finding that way, not charging at the destination. This skill charts the way as a shared map on the repo's issue tracker, then works its decision tickets — questions whose resolution is a decision, not slices of a build to execute — one at a time until the route is clear.
2
3	The destination varies per effort, and naming it is the first act of charting — it shapes every ticket. It might be a spec to hand off and iterate on, a decision to lock before planning starts, or a change made in place like a data-structure migration. The map is domain-agnostic — engineering work, course content, whatever fits the shape.
4
5	## Plan, don't do
6
7	Wayfinder is planning by default: each ticket resolves a decision, and the map is done when the way is clear — nothing left to decide before someone goes and does the thing. The pull to just do the work is usually the signal you've reached the edge of the map and it's time to hand off. An effort can override this in its Notes — carrying execution into the map itself — but absent that, produce decisions, not deliverables.
8
9	## Refer by name
10
11	Every map and ticket is an issue, so it has a name — its title. In everything the human reads — narration, the map's Decisions-so-far — refer to it by that name, never by a bare id, number, or slug. A wall of `#42, #43, #44` is illegible; names read at a glance. The id and URL don't vanish — a name wraps its link — but they ride inside the name, never stand in for it.
12
13	## The Map
14
15	The map is a single issue on this repo's issue tracker, labelled `wayfinder:map` — the canonical artifact. Its tickets are child issues of the map.
16
17	The map is an index, not a store. It lists the decisions made and points at the tickets that hold their detail; a decision lives in exactly one place — its ticket — so the map never restates it, only gists it and links.
18
19	Where the map, its child tickets, blocking, and frontier queries physically live is tracker-specific. The issue tracker should have been provided to you — run `/setup-matt-pocock-skills` if not. Consult the tracker doc's "Wayfinding operations" section for how _this_ repo expresses them. If no tracker has been provided, default to the local-markdown tracker.
20
21	### The map body
22
23	The whole map at low resolution, loaded once per session. Open tickets are not listed — they are open child issues, found by query.
24
25	```markdown
26	## Destination
27
28	<what reaching the end of this map looks like — the spec, decision, or change this effort is finding its way to. One or two lines; every session orients to it before choosing a ticket.>
29
30	## Notes
31
32	<domain; skills every session should consult; standing preferences for this effort>
33
34	## Decisions so far
35
36	<!-- the index — one line per closed ticket: enough to judge relevance, then zoom the link for the detail the ticket holds -->
37
38	- [<closed ticket title>](link) — <one-line gist of the answer>
39
40	## Not yet specified
41
42	<!-- see "Fog of war": in-scope fog you can't ticket yet; graduates as the frontier advances -->
43
44	## Out of scope
45
46	<!-- see "Out of scope": work ruled beyond the destination; closed, never graduates -->
47	```
48
49	### Tickets
50
51	Each ticket is a child issue of the map; the tracker's issue id is its identity. Its body is the question, sized to one 100K token agent session:
52
53	```markdown
54	## Question
55
56	<the decision or investigation this ticket resolves>
57	```
58
59	Each ticket carries a `wayfinder:<type>` label — one of `research`, `prototype`, `grilling`, `task` (see [Ticket Types](#ticket-types)).
60
61	A session claims a ticket by assigning it to the dev driving the map, first, before any work, so concurrent sessions skip it. That assignee _is_ the claim: an open, unassigned ticket is unclaimed.
62
63	Blocking uses the tracker's native dependency relationship — essential because it renders the frontier _visually_ in the tracker's own UI, so the human sees what's takeable without opening the map. Only a tracker that lacks native blocking falls 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.
64
65	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.
66
67	## Ticket Types
68
69	Every ticket is either HITL — human in the loop, worked with a human who speaks for themselves — or AFK, driven by the agent alone. A HITL ticket only resolves through that live exchange; the

tt-a1iPublisher · 26 listings

Preview

tt-a1i/matt-skills-with-to-goal

A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the **destination** isn't visible yet. Wayfinding is about fi

The destination varies per effort, and naming it is the first act of charting — it shapes every ticket. It might be a spec to hand off and iterate on, a decisio

## Plan, don't do

Wayfinder is **planning** by default: each ticket resolves a decision, and the map is done when the way is clear — nothing left to decide before someone goes an

Repott-a1i/matt-skills-with-to-goal

LicenseMIT

TypeSkills

CategoryPlanning

UpdatedJul 2026

Repo stars16

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

wayfinder

16stars3forks

View on GitHub

How to install wayfinder?

tt-a1i/matt-skills-with-to-goal/wayfinder

$npx -y skills add tt-a1i/matt-skills-with-to-goal --skill wayfinder

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the destination isn't visible yet. Wayfinding is about finding that way, not charging at the destination. This skill charts the way as a shared map on the repo's issue tracker, then works its decision tickets — questions whose resolution is a decision, not slices of a build to execute — one at a time until the route is clear.
2
3	The destination varies per effort, and naming it is the first act of charting — it shapes every ticket. It might be a spec to hand off and iterate on, a decision to lock before planning starts, or a change made in place like a data-structure migration. The map is domain-agnostic — engineering work, course content, whatever fits the shape.
4
5	## Plan, don't do
6
7	Wayfinder is planning by default: each ticket resolves a decision, and the map is done when the way is clear — nothing left to decide before someone goes and does the thing. The pull to just do the work is usually the signal you've reached the edge of the map and it's time to hand off. An effort can override this in its Notes — carrying execution into the map itself — but absent that, produce decisions, not deliverables.
8
9	## Refer by name
10
11	Every map and ticket is an issue, so it has a name — its title. In everything the human reads — narration, the map's Decisions-so-far — refer to it by that name, never by a bare id, number, or slug. A wall of `#42, #43, #44` is illegible; names read at a glance. The id and URL don't vanish — a name wraps its link — but they ride inside the name, never stand in for it.
12
13	## The Map
14
15	The map is a single issue on this repo's issue tracker, labelled `wayfinder:map` — the canonical artifact. Its tickets are child issues of the map.
16
17	The map is an index, not a store. It lists the decisions made and points at the tickets that hold their detail; a decision lives in exactly one place — its ticket — so the map never restates it, only gists it and links.
18
19	Where the map, its child tickets, blocking, and frontier queries physically live is tracker-specific. The issue tracker should have been provided to you — run `/setup-matt-pocock-skills` if not. Consult the tracker doc's "Wayfinding operations" section for how _this_ repo expresses them. If no tracker has been provided, default to the local-markdown tracker.
20
21	### The map body
22
23	The whole map at low resolution, loaded once per session. Open tickets are not listed — they are open child issues, found by query.
24
25	```markdown
26	## Destination
27
28	<what reaching the end of this map looks like — the spec, decision, or change this effort is finding its way to. One or two lines; every session orients to it before choosing a ticket.>
29
30	## Notes
31
32	<domain; skills every session should consult; standing preferences for this effort>
33
34	## Decisions so far
35
36	<!-- the index — one line per closed ticket: enough to judge relevance, then zoom the link for the detail the ticket holds -->
37
38	- [<closed ticket title>](link) — <one-line gist of the answer>
39
40	## Not yet specified
41
42	<!-- see "Fog of war": in-scope fog you can't ticket yet; graduates as the frontier advances -->
43
44	## Out of scope
45
46	<!-- see "Out of scope": work ruled beyond the destination; closed, never graduates -->
47	```
48
49	### Tickets
50
51	Each ticket is a child issue of the map; the tracker's issue id is its identity. Its body is the question, sized to one 100K token agent session:
52
53	```markdown
54	## Question
55
56	<the decision or investigation this ticket resolves>
57	```
58
59	Each ticket carries a `wayfinder:<type>` label — one of `research`, `prototype`, `grilling`, `task` (see [Ticket Types](#ticket-types)).
60
61	A session claims a ticket by assigning it to the dev driving the map, first, before any work, so concurrent sessions skip it. That assignee _is_ the claim: an open, unassigned ticket is unclaimed.
62
63	Blocking uses the tracker's native dependency relationship — essential because it renders the frontier _visually_ in the tracker's own UI, so the human sees what's takeable without opening the map. Only a tracker that lacks native blocking falls 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.
64
65	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.
66
67	## Ticket Types
68
69	Every ticket is either HITL — human in the loop, worked with a human who speaks for themselves — or AFK, driven by the agent alone. A HITL ticket only resolves through that live exchange; the

tt-a1iPublisher · 26 listings

Preview

tt-a1i/matt-skills-with-to-goal

A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the **destination** isn't visible yet. Wayfinding is about fi

The destination varies per effort, and naming it is the first act of charting — it shapes every ticket. It might be a spec to hand off and iterate on, a decisio

## Plan, don't do

Wayfinder is **planning** by default: each ticket resolves a decision, and the map is done when the way is clear — nothing left to decide before someone goes an

Repott-a1i/matt-skills-with-to-goal

LicenseMIT

TypeSkills

CategoryPlanning

UpdatedJul 2026

Repo stars16

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type