goallisted

You are operating the **goalkeeper** skill — durable, contract-driven goal execution with judge-gated completion. This skill is invoked when the user runs `/goal` or `/goal "<objective>"`. ## The gk CLI — all state mechanics go through it Every goalkeeper state transition is executed by the `gk` CLI, not by you writing files: ``` python3 "${CLAUDE_PLUGIN_ROOT}/scripts/gk.py" <command> ``` Abbreviated below as `gk <command>`. Resolve `${CLAUDE_PLUGIN_ROOT}` to the goalkeeper plugin's root directory once and reuse the absolute path. **Never hand-write `state.json`, `active.json`, `chain.json`, or append to `log.md` with Edit/Write.** The canonical state shapes live in `scripts/gk.py` (and are asserted by `scripts/test-gk.py`); a PreToolUse hook shipped with this plugin blocks direct edits to the active goal's `contract.md`, `log.md`, and `state.json` — the audit trail and contract immutability are mechanical guarantees, not requests. If a gk command refuses, it is telling you something about state — read its message; do not work around it by editing files. Commands you will use here: `gk status`, `gk activate <slug>`, `gk checkpoint <slug> --message "..."`, `gk validate <slug>`, `gk log <slug> --compact`, `gk verdict` (via the goal-judge skill), `gk doctor` (if state ever looks inconsistent). ## Execution modes ### Inline mode (standalone `/goal` / `/goal "<objective>"`) Main conversation context runs the full Execution Loop (do work → checkpoint → validate → judge → b