retro

Generate structured retrospective documents with actionable items and archival output.

Updated Feb 13, 2026

Search Tags:#workflow #template #retrospective #scopes #action-items #retro #team-improvement

Ready to run

npx skills add https://github.com/Rwb3n/callsheet --skill retro-rwb3n

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Rwb3n/callsheet/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/Rwb3n/callsheet --skill retro-rwb3n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrospective sessions often produce vague insights; this Skill guides teams to generate structured, grounded summaries and concrete actions.

Core Features & Use Cases

Structured three-section retro template aligned to real scopes (work items, slices, chapters, arcs, or general sessions)
Enforces action registers with DoD-grounded items and mindful scope grounding
Outputs to a standard archival path and provides a repeatable process for future sessions

Quick Start

Provide a scope (e.g., S1 or CS-WORK-007) and run the retro to generate a fully filled retrospective document.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I create a structured retrospective with actionable items?▼

A structured retrospective turns team reflections into concrete actions by applying a repeatable template with defined action registers, work item grounding, and standard archival output.

What is the best way to ground retrospective summaries in actual project context?▼

Grounding retrospective summaries requires specifying scopes like work items, slices, chapters, or arcs, ensuring the output reflects relevant project context rather than vague insights.

How do I generate a retrospective document for a specific work item scope?▼

You can generate a retrospective document by providing a specific scope identifier like S1 or CS-WORK-007, which the system uses to fill a structured three-section template automatically.

Does this retrospective template enforce definition of done considerations for action items?▼

Yes, the retrospective template enforces action registers that require definition of done considerations, ensuring team reflections produce measurable, actionable improvements rather than open-ended tasks.

Can I use general sessions for retrospectives if I don't have specific work item scopes?▼

Yes, you can run retrospectives using general sessions if specific work item scopes are unavailable, allowing teams to still capture structured summaries and actionable improvements.

Why should I use an automated retrospective template over manual note-taking?▼

Automated retrospective templates solve the problem of vague insights by enforcing a repeatable process with structured sections, grounded action registers, and consistent archival paths for future reference.