Manage work items as machine-checkable cards in a Kanban-style deck.
npx skills add https://github.com/zauberzeug/game-of-cards --skill deck-zauberzeug
Please help me install this Agent Skill. Skill: deck Source: https://github.com/zauberzeug/game-of-cards/tree/main/openclaw-plugin/skills/deck Command: npx skills add https://github.com/zauberzeug/game-of-cards --skill deck-zauberzeug
The Deck provides a single, structured surface to model work as persistent, machine-checkable cards, enabling AI agents and humans to collaborate with clear lifecycle contracts and durable cross-references.
Create a new card with the create-card skill and drive it through open, active, and done with the advance-card and finish-card skills.
High-intent search queries and answers about installing and using this skill.
You can manage persistent work items for AI agent collaboration by modeling tasks as machine-checkable cards within a Kanban-style deck, enabling clear lifecycle contracts and durable cross-references between humans and AI. This provides a structured surface for auditable workflows.
A machine-checkable card workflow tracks task lifecycles using frontmatter-based status and a machine-enforceable Definition of Done (DoD) within a stable directory structure. This enables gate-based workflow transitions and terminal states for auditable task orchestration.
Automate Kanban task transitions by applying skills like advance-card and decide-card to drive items through open, active, and done states. These skills enforce frontmatter-defined DoD gates and manage workflow transitions across the deck.
Yes, you can coordinate human and AI agent workloads across queues using multiple operation modes including session, autonomous, and andon-cord. These modes preserve card history while orchestrating collaborative work across different queues.
Yes, card-based task orchestration supports autonomous operation modes alongside session and andon-cord modes. This allows AI agents to independently manage workloads while maintaining persistent context and lifecycle tracking within the deck structure.
Directory-based lifecycle management relies on a stable deck/ surface where each card resides in deck/<title>/, which requires consistent frontmatter maintenance. Terminal states and gate-based transitions must be strictly enforced to prevent lifecycle tracking errors.
agilebydesignConvert DO/DO NOT rules into automated scanner checks.
zauberzeugEnforce documented status transitions for GoC deck cards via CLI commands.
mishahaninDeposit email drafts into a gated action queue for human approval.
papeete-consulting-labGenerate a kanban board from task files with derived workflow states.
