retro

Name: retro
Availability: InStock
Author: motwakorb

Generate a multi-persona session retrospective and write it to a markdown file.

2|Updated Apr 19, 2026

Search Tags:#documentation #beads #retrospective #perspectives #team-learning #session-review

Ready to run

npx skills add https://github.com/MotWakorb/claude-agent-dev-team --skill retro-motwakorb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/MotWakorb/claude-agent-dev-team/tree/main/retro
Command: npx skills add https://github.com/MotWakorb/claude-agent-dev-team --skill retro-motwakorb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrospectives are essential for continuous improvement but are often informal, incomplete, or siloed. This Skill ensures a structured, comprehensive end-of-session review that includes input from every persona involved.

Core Features & Use Cases

Structured retrospectives: Generates a formal, multi-perspective report capturing what went well, what could improve, what was missed, and durable lessons.
Multi-persona input: Aggregates insights from all relevant personas and stakeholders to surface conflicts and align on improvements.
Output-ready artifact: Writes a markdown retrospective to the designated ~/retros/ path with a consistent naming convention for easy traceability.

Quick Start

Instruct the Skill to generate a retrospective for the current session by invoking the skill with the appropriate session context.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate an automated retrospective for a team learning session?▼

An automated retrospective captures session insights by aggregating inputs from all invoked personas and stakeholders, generating a structured markdown report highlighting what went well, what needs improvement, and durable lessons.

What is the best way to document multiple persona perspectives during a session review?▼

Documenting multiple persona perspectives involves systematically gathering inputs from every invoked stakeholder to surface conflicting viewpoints, align on actionable improvements, and compile a comprehensive multi-perspective session review artifact.

How do I save a structured retrospective report to a markdown file?▼

Saving a structured retrospective report writes the generated insights directly to a markdown file in the designated local directory, using a consistent date-time and topic-based naming convention for reliable traceability.

Can I use a session review skill if no specific personas were invoked?▼

A session review skill functions best when invoked personas provide distinct inputs, but it still generates a retrospective capturing the general session context, relevant stakeholder viewpoints, and actionable insights for continuous improvement.

What are the limitations of automated end-of-session retrospectives?▼

Automated retrospectives rely entirely on the conversation context available at generation time, meaning they cannot capture offline discussions or unrecorded stakeholder feedback, limiting the overall comprehensiveness of the session review.