godmodelisted

# Godmode ## Outcome Establish what is true now, choose one bounded workflow, and leave locally verifiable continuity without placing operational memory in tracked project files. ## Entry sequence 1. Identify the project root and read its active instructions. 2. Resolve the bundled `scripts/godmode.py` from the plugin root: use `$GROK_PLUGIN_ROOT` if set, else `$CLAUDE_PLUGIN_ROOT` if set, else the directory two levels above this skill file. Do not assume the user's project contains this script. 3. If Godmode is initialized, run `<plugin-root>/bin/godmode --project <root> context status` (`bin\godmode.cmd` on Windows). The shim probes `python3`, then `python`, then `py`, and honours `GODMODE_PYTHON`; a bare `python` does not exist on stock macOS, so never write it into a command. 4. For a new or uncertain session, use `resume --refresh`; otherwise use `resume`. 5. Separate observed facts, declared intent, assumptions, conflicts, and open obligations. 6. Route to the narrowest specialist below. ## Day one on a host whose reach is PARTIAL or SOFT `godmode hooks status` (or the first line of `session open`) names the host's reach. Where the pre-tool gate is not HARD, the ceremony above buys nothing the host will enforce; the path is six verbs and no more: `init` once, `session open`, `resume`, `remember`, `claim`, `checkpoint`. Everything else is `godmode guide --tier N` when a task asks for it. On Grok the session brief rides the next allowed call and a ref