geniuslisted

# The Genius Map The map answers three questions: where every piece of work stands, what runs next, and which genius went missing when something feels wrong. It routes; it never builds. ## The flow Every piece of work travels through six geniuses, in three pairs: | Stage | Genius | Command | Skipping it looks like | |---|---|---|---| | **Ideation** | Wonder — question the work | `/wonder` | building exactly the wrong thing | | | Invention — generate options | `/invent` | anchoring on the first idea | | **Activation** | Discernment — judge and choose | `/discern` | plausible-but-wrong ships | | | Galvanizing — mobilize into slices | `/galvanize` | a plan nobody can start | | **Implementation** | Enablement — build with tight loops | `/enable` | flying blind until a big-bang reveal | | | Tenacity — finish with evidence | `/tenacity` | "done" that isn't | State lives in `.genius/<slug>.md` — the bounded snapshot a cold session reads whole — with its history appended to `.genius/<slug>.log.md` beside it (the `genius-file` skill owns the discipline). Each stage ends when its one threshold is honestly true; each is a command the user types, and one they don't type simply doesn't run — its absent section is the record. Four layers run underneath: the `domain-glossary` skill keeps the project's shared language in `CONTEXT.md`, the `decision-record` skill keeps the index of its settled decisions in `.genius/DECIDED.md`, the `blindspot` skill hunts the unknowns the stages can't re