Read The Map

Where does this map stand, and what comes next on it? This skill answers that for one map, and it owns the checklist for what reading a map means — everything else that needs a map read, /whats-next and /check-wayfinder-maps included, follows this list rather than inventing its own.

This skill never writes. No claims, no comments, no closes, no map edits. It reads and reports. If the reading turns up work, hand it to /wayfinder, /decisions-to-specs, or /specs-to-tickets.

Tracker conventions

Read the repo's issue-tracker doc (docs/agents/issue-tracker.md), specifically its Wayfinding operations section, for how this repo expresses maps, child tickets, and blocking. This is a per-repo lookup, not a per-map one. Defaults, where the doc is silent:

• Map — an issue labelled wayfinder:map
• Child ticket — a GitHub sub-issue of the map, labelled wayfinder:<type>
• Blocking — GitHub native issue dependencies; fall back to a Blocked by: #n line in the body
• Claimed — the ticket has an assignee

The checklist

Everything below happens for the map in hand. Items 2 and 3 come from list-level data — title, state, labels, assignee, dependencies — which a tracker returns without opening anything; item 1 is the one body you always read.