goal-chainlisted

You are operating the **goal-chain** skill. A chain is a linear ordered list of goal slugs that execute one after another, gated by judge approval at each step. The gk CLI (`python3 "${CLAUDE_PLUGIN_ROOT}/scripts/gk.py"`, abbreviated `gk`) owns all chain mechanics: parsing and validating the chain file, cursor movement, link approvals, and next-goal activation. You orchestrate: spawn executor → spawn judge → let `gk verdict` apply the outcome → act on what it prints. ## Modes 1. **Start mode** — `args` is a non-empty path to a chain file. Begin a new chain. 2. **Status mode** — `args == "status"` or a chain exists and the user asks plainly. Show progress. (There is no separate "advance mode" anymore — `gk verdict <slug> approve` advances the cursor atomically as part of applying the verdict.) ## Start mode Triggered by `/goal-chain "<path/to/chain.md>"`. ### 1. Start the chain ``` gk chain-start <path/to/chain.md> ``` gk parses the file (frontmatter `name:` plus a numbered or bulleted slug list, `#` comments stripped), verifies every slug has a `contract.md` (a missing contract aborts start — prep all contracts up front so the chain definition is reviewable), refuses to start over an active goal or chain, writes `chain.json`, and activates the first slug. It prints `NEXT: <slug>` on success; on refusal, relay its message to the user (usually: run `/goal-prep` for missing slugs, or `/goal-clear` first). ### 2. Spawn the executor subagent Chains run per-goal implemen