genius

# 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 `genius-file` skill owns the format). Each stage ends in a gate; the next stage checks it. Skips are allowed but always recorded — that's how gaps stay visible. Underneath the flow run two cross-cutting layers. The `domain-glossary` skill keeps `CONTEXT.md`, the project's shared language — `/wonder` and `/discern` drive it actively; every other stage just speaks it. Unlike work files, it's project-level: it compounds across all work. The `blindspot` skill hunts the unknowns the stages can't reach — a read-only territory pass before unfamiliar work, judgment taught before a choice is...