kickofflisted

# Kick off GoC in this repo This skill is the **host-agnostic onboarding dialog**: it introduces GoC, asks a few focused questions, then runs `goc install` to scaffold project state. It runs **idempotently** — every stage detects on-disk state before asking, so a re-run on a partially set-up repo only asks for the answers it cannot already derive. The body covers what every host needs. Host-specific UX (permission prompts, plugin install cadence, private-notes file) lives in a complementary per-host skill that runs after this one — for example, `claude-kickoff` on Claude Code. ## Stage 0 — state detection sweep Read all of the on-disk signals at once. Each subsequent stage will skip its question(s) when the corresponding signal is already present. ```bash ls .game-of-cards/deck/ 2>/dev/null && echo "DECK_EXISTS" || echo "deck_missing" which goc 2>/dev/null && echo "GOC_ON_PATH" || echo "goc_missing" grep -l '<!-- BEGIN GOC' AGENTS.md CLAUDE.md CLAUDE.local.md 2>/dev/null && echo "BRIEFING_MERGED" || true grep -E '^autonomy:' .game-of-cards/config.yaml 2>/dev/null && echo "AUTONOMY_SET" || true [ -d .git ] && echo "GIT_REPO" || echo "git_missing" ``` Route on the results: - **`DECK_EXISTS` + `AUTONOMY_SET`** → report "GoC is already initialized in this repo — deck is live." and **stop**. Do not continue. This is the silent-exit branch the skill description promises. - **`DECK_EXISTS` without `AUTONOMY_SET`** → install completed previously but the autonomy question