narrative-sensemakinglisted
Install: claude install-skill cdeust/zetetic-team-subagents
# Narrative Sensemaking
**Problem shape:** the material is an account — an incident write-up, a user
journey, a roadmap story, a vendor claim, a postmortem — and the work is to
recover its structure: which functions occur in which order, which roles are
filled, where the sequence breaks its own grammar, and whether the account is
even structurally possible. Paradigmatic/causal analysis is the wrong mode here
and produces confident nonsense when forced.
## Relevant geniuses
| Agent | Use when |
|---|---|
| [bruner](../../agents/genius/bruner.md) | the question is "what happened and what did it mean?" — decide narrative vs paradigmatic mode explicitly, then analyze the breach of the canonical script that made the event tellable |
| [propp](../../agents/genius/propp.md) | a sequential process (workflow, pipeline, user journey, incident response) needs its invariant functions extracted, its roles abstracted from their current occupants, and its gaps found by grammar rather than by inspection |
| [ibnkhaldun](../../agents/genius/ibnkhaldun.md) | a claim sounds authoritative but may be structurally impossible — filter on structural plausibility *before* evaluating the source; check whether the reported thing could occur at that scale at all |
## Invocation
1. Pick the best-fit agent above. If two or more fit, run
`tools/genius-invoker.sh route "<problem>"` and take the top ranked match.
2. Load it: `tools/genius-invoker.sh invoke <agent> "<problem>"`, then read
`agents/g