Git
v1.0.0

Kick off GoC in this repo

by @zauberzeug0 pulls
URLopenbooklet.com/s/kick-off-goc-in-this-repo
Pinnedopenbooklet.com/s/[email protected]
APIGET /api/v1/skills/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

21 skills from this repozauberzeug/game-of-cards
Kick off GoC in this repoviewing
Advance a card.claude/skills/advance-card/SKILL.md

Every status transition is a documented agreement, not a silent flag flip — the reason lives on disk: in the body for terminal transitions, in the commit message for mid-flight ones. Mutate a card's status — everything except `done`, which is `Skill(finish-card)`'s DoD-gated contract. Read the c

advance-card.codex/skills/advance-card/SKILL.md

Mutate a card's status (everything except done — that is finish-card's job), record relationship edges, or set the goc wait impediment overlay. AUTO-INVOKE on "I'll start on X", "mark this disproved", "supersede with Z", "make this depend on Y".

audit-deck.codex/skills/audit-deck/SKILL.md

Hunt for one previously-undocumented defect, doc drift, missing test, or inconsistency; file it via Skill(create-card). AUTO-INVOKE on "find me a bug", "audit X", "check for inconsistencies", or /audit-deck. Inconsistencies are the primary lead.

card-schemacodex-plugin/skills/card-schema/SKILL.md

Card schema reference — fields, status/stage/contribution/human_gate enums, canonical tags, DoD detection, relationship invariants, title convention. AUTO-INVOKE when other deck skills need schema context, or when the user asks about field semantics, status lifecycle, DoD format, or card titling.

Close a cardclaude-plugin/skills/finish-card/SKILL.md

Scrum's **Definition of Done** as a machine-checkable closure contract: `goc done` counts unchecked boxes and refuses to flip the status while any remain. The ticked checkbox list is the audit trail.

codex-kickoff.codex/skills/codex-kickoff/SKILL.md

Codex-specific complement to the generic kickoff skill — install the GoC Codex plugin from the repo marketplace, explain hook activation, verify the goc CLI path. AUTO-INVOKE after Skill(kickoff) completes in Codex, or on "finish kickoff for Codex" / "set up Codex plugin".

create-card.codex/skills/create-card/SKILL.md

File a new card with frontmatter and a DoD scaffold BEFORE implementation — the body is the briefing the next reader needs to act cold. AUTO-INVOKE on "let's do X", "implement Y", "fix Z", a described bug, a requested feature, or ANY new persistent work item.

Decide a cardopenclaw-plugin/skills/decide-card/SKILL.md

The Andon-cord loop: `Skill(pull-card)` raises `human_gate` (`none → decision` / `session`) when it hits a question only a human can answer; this skill lowers the gate back to `none` in one cheap action. Status stays `open`, so the next `pull-card` claims and implements per the recorded decision.

decide-card.codex/skills/decide-card/SKILL.md

Record a decision (what + why) on a parked card and lower the human gate from decision or session to none. AUTO-INVOKE on "I decided X", "let's go with Y", "approved", or any resolution of a parked card — the human's one-action handoff so pull-card can resume.

deck.codex/skills/deck/SKILL.md

Front door for the deck — the operating substrate for ALL persistent work. AUTO-INVOKE when the user references the deck/methodology/workflow, or at session start as a reminder that persistent work flows through Skill(create-card) → Skill(advance-card) → Skill(finish-card).

File a new cardopenclaw-plugin/skills/create-card/SKILL.md

A card is a self-contained briefing for the next reader — human or agent — written so the work can be picked up cold: its own evidence, its own framing, its own closure contract (the DoD). Scaffold a `deck/<title>/` dir with valid frontmatter, an empty `log.md`, and a placeholder DoD that `Skill

Finish kickoff on Claude Codeclaude-plugin/skills/claude-kickoff/SKILL.md

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 C

Finish kickoff on Codexgoc/templates/skills/codex-kickoff/SKILL.md

The generic `kickoff` skill is host-agnostic: it introduces GoC, asks where the briefing should live, and scaffolds `.game-of-cards/`. This complement handles Codex-specific plugin setup.

Finish kickoff on OpenClawgoc/templates/skills/openclaw-kickoff/SKILL.md

The generic `kickoff` skill is host-agnostic: it introduces GoC, runs the persona dialog, asks about the AGENTS.md merge, and runs `goc install` to scaffold `.game-of-cards/`. This complement handles everything OpenClaw-specific that the generic kickoff intentionally leaves alone:

finish-cardcodex-plugin/skills/finish-card/SKILL.md

Close a card with DoD enforcement and a log.md closure entry — goc done refuses to close with any unchecked box. AUTO-INVOKE on "done", "close this", "finish X", "ship it", or when work satisfies a card's DoD. For every other status change, use advance-card.

pull-cardopenclaw-plugin/skills/pull-card/SKILL.md

Pull the highest-leverage `human_gate: none` open card off the queue, claim it, work it, close it, commit. AUTO-INVOKE when the user says "drain the queue", "pull a card", "let the agents work", "autonomous mode", "make progress", or when invoked via /loop or /schedule.

Refine the deckgoc/templates/skills/refine-deck/SKILL.md

Every iteration the BOARD gets better, not just the code on it: this skill is the recurring hygiene tax that keeps the deck's read-pattern guarantee alive as filing slows down and rot accumulates. The hook above may extend the flow with project-specific categories or thresholds (scope rules in `refe

refine-deckcodex-plugin/skills/refine-deck/SKILL.md

Deck hygiene pass — retag stale cards, prune 90-day unverified parks, surface defunct references, orphaned dependencies, and jargon titles. AUTO-INVOKE on "tidy up the deck", "hygiene pass", "clean up the queue", or /refine-deck. The board itself gets refactored each iteration.

Scan the deckopenclaw-plugin/skills/scan-deck/SKILL.md

Kanban's first practice (Anderson): **make work visible**. You cannot manage what you cannot see, and a swarm of /loop iterations cannot prioritize against state it has to reconstruct from chat. This skill renders the board for whoever's looking — human-supportive triage, filtered queues, kanban c

scan-deck.codex/skills/scan-deck/SKILL.md

Browse the deck — supportive triage view, filtered queues, kanban board, JSON dump, decision Q&A. Read-only by default. AUTO-INVOKE on "what's open", "show me the deck", "kanban view", or "decisions to make" — and ALWAYS before Skill(create-card) to dedup against existing titles.

Auto-indexed from zauberzeug/game-of-cards

Are you the author? Claim this skill to take ownership and manage it.

Related Skills

@openbooklet

graceful-error-recovery

Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.

1.1K0
@openbooklet

audience-aware-communication

Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.

1.1K0
@openbooklet

Refactoring Expert

Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.

600
@openbooklet

Research Expert

Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.

600
@openbooklet

clarify-ambiguous-requests

Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.

1.1K0
@openbooklet

structured-step-by-step-reasoning

Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.

1.1K0