pull-card

Pull and complete the highest-leverage open card with human_gate none.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Autonomous card pull: claim and work end-to-end on a single card.
  • Guardrails and gates: soft lock, decision gates, and DoD validation before closure.
  • Commit and reflect: close the card and commit results to the deck.
  • Works with the goc CLI to manage queue state and card life cycle.

Quick Start

Ask the agent to pull the next available card with human_gate none and begin work.

Frequently Asked Questions about pull-card

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

FAQPage Schema
How do I autonomously pull and work on Kanban cards without human intervention?

You can autonomously pull and work on Kanban cards by triggering a drain-queue or autonomous mode command. The agent claims the highest-leverage open card with human_gate: none, works it end-to-end, and closes it with a final commit.

What is a pull card workflow in autonomous software engineering?

A pull card workflow is an autonomous process where agents drain the queue by claiming the highest-leverage open card, executing the work end-to-end, and closing it with a final commit without human gating.

How do I set up autonomous agents to drain my Kanban queue?

To drain your Kanban queue, invoke autonomous operation modes via /loop or /schedule, or instruct agents to make progress. The system then pulls and processes cards continuously, respecting soft locks and gate decisions.

Do I need the goc CLI to manage autonomous card workflows?

Yes, the goc CLI is required to manage queue state and the card life cycle. It enforces project-specific rubrics via hooks and requires Definition of Done validation before closure.

What guardrails apply when agents work cards autonomously?

Guardrails include soft locks, decision gates, and Definition of Done validation before closure. These ensure autonomous agents respect gate decisions and project rubrics while processing cards without human intervention.

Why does my autonomous card workflow skip certain open cards?

The workflow skips cards that do not have human_gate: none. It specifically pulls the highest-leverage open cards available for autonomous processing, leaving gated cards for human review.