retro-botlisted

Run an agile-style sprint retrospective on a completed Claude collaboration session. Use this skill after finishing a piece of work with Claude — a scope of work, a data analysis, a content build, a code session, a Cowork task — to reflect together on what worked, what didn't, and what to change. Triggers on: "let's do a retro", "run a retro", "retrospective", "retro-bot", "what worked well", "what could we improve", "session review", "what should we do differently", "let's debrief", or any request to reflect on a completed Claude session and extract improvements. The skill produces a collaborative retro board, maps issues to actionable file changes (skill updates, Claude.md edits, process changes), applies those changes using proper versioning, and saves a dated snapshot to a user-configured archive directory — building a permanent audit trail of every retro run and its outcomes. Always use this skill rather than improvising a retro.
cometogather/retro-bot · ★ 10 · AI & Automation · score 79

Install: claude install-skill cometogather/retro-bot

# Retro-Bot A skill for running lightweight agile retrospectives on Claude collaboration sessions — making the process of working with Claude incrementally better over time. The core loop: after you and Claude finish a piece of work, you take a few minutes to ask three questions together: - **What worked well?** (keep doing this) - **What didn't work well?** (friction, rework, confusion, wasted tokens) - **What should we change?** (concrete improvements to skills, prompts, or process) Changes are applied immediately and every retro is saved as a snapshot to a persistent archive. Over time, this builds a running audit trail of how your Claude workflow has evolved — and compounds into a setup that gets meaningfully faster with each session. --- ## Phase 0 — Archive Directory Setup (first run only) Before the retro begins, check whether a retro archive directory has been configured. Look in Claude.md for a block like this: ``` ## Retro-Bot archive_dir: [path] ``` **If it's already set:** proceed directly to Phase 1. No need to ask again. **If it's not set:** ask the user once, clearly: > "Before we start — where do you want to save retro snapshots? This is a one-time > setup. Give me a folder path (e.g. `H:\My Drive\Retros` or `~/Documents/retros`) > and I'll save every retro there automatically going forward." Once the user provides a path: 1. Add the following block to Claude.md (create the file if it doesn't exist): ``` ## Retro-Bot archive_dir: [the path