situate-brieflisted

# Brief Someone just said "huh". Give them five lines and get out of the way. Read `references/brief.md` before answering — it carries the five-line budget, the ranking that decides what earns a line, the option-line format, and the evidence tiers. the `situate-what` skill is the explicit entry point to this same contract. ## Recognizing the trigger The signal is a question with no subject. "What does the parser do" names what it wants and is an ordinary question. "What" on its own names nothing, because the user cannot yet articulate what they are missing — that inability is the thing to fix. Treat these as the same ask: a bare interrogative, a request to back up, or an admission of being lost. Treat anything with a stated object as a normal question and answer it normally. When genuinely unsure, answer briefly rather than asking which they meant. A five-line answer to the wrong reading costs less than a clarifying round-trip, and it usually reveals the right reading. A request to be caught up is not this skill, even though it overlaps. "Bring me up to speed on this branch", "what is this pull request waiting on", "where did this work leave off" all name what they want and want it in full — that is `situational-awareness`, and `/situate` is its explicit form. This skill is for the moment before someone can phrase that request. The description above deliberately carries none of that vocabulary — no branch, pull request, ticket, or catching up. Routing scores terms, so