standup

List active and blocked cards with blocker reasons from deck data.

6|Updated May 4, 2026

Search Tags:#workflow #agile #status #read-only #standup #cards #deck

Ready to run

npx skills add https://github.com/zauberzeug/game-of-cards --skill standup-zauberzeug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: standup
Source: https://github.com/zauberzeug/game-of-cards/tree/main/openclaw-plugin/skills/standup
Command: npx skills add https://github.com/zauberzeug/game-of-cards --skill standup-zauberzeug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Daily standups require a concise, up-to-date view of the work in the deck. This skill reads the deck state and surfaces what is active, what is blocked (with blocker notes), what has recently closed from log.md, and what items are waiting on human gates, all without mutating any cards.

Core Features & Use Cases

Read-only standup view: lists active, blocked, and recently closed cards.
Blocker visibility: shows blocker reasons from the card body.
Gate visibility: surfaces cards waiting on a decision or session from human_gate flags.

Quick Start

Speak a standup query like what's up to receive a read-only deck standup report.

Frequently Asked Questions about standup

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

FAQPage Schema

How do I get a quick daily standup report for active and blocked cards?▼

To get a daily standup report, you can prompt the system with a common standup query to receive a read-only summary listing active cards, blocked cards with reasons, and recent closures from the log.

What is the best way to track blocked cards and human gates for an agile workflow?▼

Tracking blocked cards and human gates involves reading deck data to surface items with blocker notes and cards awaiting human decisions, providing visibility into agile workflow constraints without mutating state.

How does a read-only standup deck readout work without changing card status?▼

A read-only standup deck readout works by querying the current deck state and log data to surface active, blocked, and recently closed items, ensuring the system reads data without mutating any cards.

Can I see what cards were closed in the last 24 hours from the deck log?▼

You can see cards closed in the last 24 hours by generating a standup summary, which surfaces closures recorded in the log.md file alongside currently active and blocked deck items.

Does the standup summary automatically trigger when I ask for a status update?▼

The standup summary auto-invokes on common standup prompts like asking what's up, immediately generating a read-only deck report without requiring manual setup or state changes.