advance-card

Enforce documented status transitions for GoC deck cards via CLI commands.

6|Updated May 4, 2026
One-click install
npx skills add https://github.com/zauberzeug/game-of-cards --skill advance-card
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advance-card
Source: https://github.com/zauberzeug/game-of-cards/tree/main/openclaw-plugin/skills/advance-card
Command: npx skills add https://github.com/zauberzeug/game-of-cards --skill advance-card

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mutating a card's status in the GoC deck requires careful coordination and an auditable trail. This skill centralizes and enforces transitions to reduce errors and keep the deck consistent.

Core Features & Use Cases

  • Enforces documented status transitions for cards (open, active, blocked, disproved, superseded) while ensuring terminal states (done) are handled by the finish-card workflow.
  • Validates the current state, applies the requested transition via the CLI (goc status / goc advance / unadvance), and records rationale in the card body when needed.
  • Provides guidance for typical Kanban flows and keeps an auditable history for review and governance.

Quick Start

Move a card to a new status with goc status <title> <new-status> or goc advance <title> --by <other> to record the transition.

Frequently Asked Questions about advance-card

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I transition a card's status in a GoC deck while keeping an auditable history?

To transition a card's status in a GoC deck with an auditable history, use the CLI to apply the state change. The skill validates the current state, enforces documented transition policies, and records rationale in the card body to ensure governance.

How does the CLI enforce Kanban workflow policies when advancing card statuses?

The CLI enforces Kanban workflow policies by validating the current state before applying any requested transition. It gates terminal transitions using Definition of Done and policy notes in the card body, restricting moves between open, active, blocked, disproved, or superseded states.

Can I move a card to a done status using the advance-card workflow?

You cannot move a card to a done status using the advance-card workflow, because terminal states are handled by the finish-card workflow. This skill is restricted to managing transitions between open, active, blocked, disproved, and superseded states.

What is the best way to document blocked or disproved card state transitions?

The best way to document blocked or disproved card state transitions is to use the CLI to apply the change, which then records the required rationale directly in the card body. This ensures an auditable trail for review and governance.

Why does advancing a card status require policy notes in the card body?

Advancing a card status requires policy notes in the card body to gate terminal transitions and enforce documented transition policies. This validation ensures an auditable commit history and maintains consistency across the Kanban deck.