whatlisted

Explain the CONCEPTS a session used, at the operator's register, grounded in what actually ran. After an agent works, you are handed results built out of vocabulary you did not choose — primitive short-names, entity slugs, library names, terms of art from the diff. `/what` names those terms, ranks them by what actually blocks understanding, defines each one, and anchors it to where it appeared and to its knowledge-graph entity. Fired mid-conversation with a short slice it degrades to the re-pitch case: "that did not land, say it again with more context and a simpler register." USE WHEN: /what, "wait what", "what did you just do", "explain that again", "I don't follow", "you lost me", "what do those terms mean", "re-pitch that", "explain the concepts", "what is all this jargon", after an autonomous arc or a long PR when the vocabulary outran the operator. NOT FOR: a summary of actions taken (that is the P1 Bridge session log); state for the next agent (that is /handoff); teaching a whole body of work to master
broomva/skills · ★ 3 · AI & Automation · score 75

Install: claude install-skill broomva/skills

# what — explain the concepts, not the timeline A session ends. The work is done and the summary is accurate, and you still cannot review the next PR in that area, because eight of the nouns were new. That gap does not close by re-reading the summary. It closes by someone naming the eight nouns and defining them. Nothing else in the stack does this. Bridge (P1) records *what happened*. `/handoff` writes *state for the next agent*. `/comprehend` runs a multi-stage teach-to-mastery loop. `/what` is the fast one: **the vocabulary of the last stretch of work, explained once, grounded in where it actually appeared.** ## The one rule > **Concepts, not chronology.** > > If the answer reads "first I did X, then Y, then Z", it is a session log and > it has failed. `/what` is organised by *idea*, ranked by *what blocks > understanding* — never by what was hardest to build or said most often. ## Scope `/what` explains **everything since you last asked** `/what`. One rule covers both cases: | You fire it | Slice | Behaviour | |---|---|---| | After a long arc | since the last `/what`, else the whole session | full concept inventory | | Right after one dense message | that message | the re-pitch case (below) | | `/what <term>` | the whole session | one concept, in depth | | `/what --scope session` | whole session, markers ignored | full inventory | **The re-pitch case.** When the slice is short or plain, the script returns an empty inventory. That is not a failure — it is the signa