claude-kickofflisted

# Finish kickoff on Claude Code The generic `kickoff` skill is host-agnostic: it introduces GoC, runs the persona dialog, asks where the briefing should live (`AGENTS.md`, `CLAUDE.md`, or `CLAUDE.local.md`), and runs `goc install --briefing-target <choice>` to scaffold `.game-of-cards/`. This complement handles everything Claude Code-specific that the generic kickoff intentionally leaves alone: - the `Bash(goc:*)` permission grant for future sessions, - the `/plugin install` (and `/plugin marketplace update`) cadence, - the minimal `CLAUDE.md` `@<chosen-file>` pointer when the briefing lives in `AGENTS.md` or `CLAUDE.local.md`, - writing GoC-managed entries into `.claude/settings.json`. Run this skill **after** the generic kickoff returns. Re-running is safe: every stage detects existing on-disk state before asking. > **Updating the plugin?** Run `/plugin marketplace update zauberzeug/game-of-cards` > before `/plugin install` — Claude Code reuses its local marketplace clone and does > not refresh it automatically. Skipping this step silently installs the old bytes. ## Stage 0 — state detection sweep Read the on-disk signals that determine which stages still have work to do: ```bash grep -l '<!-- BEGIN GOC' AGENTS.md CLAUDE.md CLAUDE.local.md 2>/dev/null ``` The first matching file (or the only matching file) is the **briefing target** — the home the generic kickoff chose. Hold that path; Stage 2 needs it. Read the project's `.claude/settings.json` and `~/.claude/se