retrospective

Cluster closed cards by tag to surface patterns, failures, and velocity metrics without mutating the deck.

6|Updated May 4, 2026

Search Tags:#retrospective #velocity #read-only #failure-modes #card-deck #pattern-clustering

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify patterns from recent closures, surface recurring failure modes, and provide velocity signals to guide improvement, all in a read-only fashion.

Core Features & Use Cases

Cluster closures by tag to surface common themes and recurring issues.
Surface failure modes and potential generalization candidates without modifying the deck.
Provide velocity metrics for completed work to support planning and improvement.
AUTO-INVOKE when user says "what have we learned", "review recent work", "any patterns lately", "look back", "retrospective", "retro", "what's our velocity", or "what keeps going wrong".

Quick Start

Use the retrospective skill to audit the last N closed cards and surface patterns.

Frequently Asked Questions about retrospective

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

FAQPage Schema

How do I surface recurring failure modes from closed cards?▼

To surface recurring failure modes from closed cards, use a retrospective tool that clusters recent closures by tag and detects patterns. This process operates on deck histories to identify common themes without modifying the underlying data.

What is pattern clustering in a retrospective analysis?▼

Pattern clustering in a retrospective analysis is the process of grouping closed card insights by tag to detect recurring issues. It surfaces common themes and proposes generalization candidates to guide team improvement.

Can I calculate velocity metrics without modifying the deck history?▼

Yes, you can calculate velocity metrics without modifying the deck history by using read-only access. The system analyzes closed histories to provide velocity signals for completed work while ensuring the deck remains untouched.

How do I review recent work and identify what keeps going wrong?▼

To review recent work and identify what keeps going wrong, run a retrospective analysis on the last N closed cards. This clusters insights by tag, surfaces recurring failure modes, and outputs safe generalization proposals.

Does the retrospective analysis require write access to the card deck?▼

No, the retrospective analysis requires only read-only access to the card deck. It operates on closed histories to surface patterns and velocity metrics without mutating the deck, ensuring safe generalization proposals.