retro

Summarize session accomplishments and issues into a structured retrospective with documentation updates.

6|Updated Feb 7, 2026

Search Tags:#documentation #retrospective #sprint #project-management #feedback-loop #knowledge-transfer #retro

Ready to run

npx skills add https://github.com/opmau/claude-code-framework --skill retro-opmau

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/opmau/claude-code-framework/tree/main/templates/.claude/skills/retro
Command: npx skills add https://github.com/opmau/claude-code-framework --skill retro-opmau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

post-session retrospectives are often informal and lose actionable insights; this skill provides a structured, repeatable way to capture accomplishments, issues, and suggested documentation updates.

Core Features & Use Cases

Structured recap: summarizes what was accomplished and what went wrong.
Documentation hygiene: checks CLAUDE.md Domain Knowledge, docs/LINEAR_SNAPSHOT.md, and docs/CURRENT_SPRINT.md for needed updates and logs carry-forward items.
Output format: generates a portable, action-oriented plan with sections for Accomplished, Issues Encountered, Proposed Documentation Updates, and Carry Forward.

Quick Start

Invoke the retro skill after a session to generate a structured retrospective and suggested documentation updates.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I structure a sprint retrospective to capture actionable insights?▼

You can structure a post-session retrospective by documenting what was accomplished, issues encountered, proposed documentation updates, and carry-forward items, ensuring traceable improvements. This generates a portable, action-oriented plan for post-session workflows.

What is the best way to automate documentation updates after a project session?▼

The best way to automate documentation updates is to check CLAUDE.md Domain Knowledge, docs/LINEAR_SNAPSHOT.md, and docs/CURRENT_SPRINT.md for needed changes based on session findings. It proposes specific updates to maintain project knowledge transfer hygiene.

How do I log carry-forward items and issues from a development sprint?▼

You log carry-forward items and issues from a development sprint by using a structured output format that categorizes issues encountered and tracks unresolved tasks. This ensures actionable insights are retained for the next project iteration.

Does this retrospective workflow require any specific project management dependencies?▼

This retrospective workflow does not require any specific project management dependencies. It operates independently to analyze session data and propose documentation updates for knowledge transfer without external integrations.

When should I run a post-session retrospective for my project?▼

Run a post-session retrospective immediately after a working session to capture what was accomplished and what went wrong. This prevents informal recaps from losing actionable insights and maintains documentation hygiene across the project.