retrospective

Facilitate structured sprint retrospectives and generate action plans.

3|Updated May 28, 2026

Search Tags:#retrospective #agile #sprint #team-collaboration #continuous-improvement #meeting-facilitation

Ready to run

npx skills add https://github.com/mahg-es/araya --skill retrospective-mahg-es

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/mahg-es/araya/tree/main/skills/retrospective
Command: npx skills add https://github.com/mahg-es/araya --skill retrospective-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Retrospective skill enables teams to hold a structured, blameless sprint retrospective to identify learnings, celebrate wins, and commit to concrete process improvements.

Core Features & Use Cases

Structured, guided reflection on what went well, what didn’t, and what to change.
Time-boxed retrospectives aligned with sprint boundaries and post-mortems for consistent cadence.
Outputs a concrete action plan and a standardized retrospective document for traceability.

Quick Start

Gather sprint data and run the three acts to produce the retrospective document at .araya/plan/spec/retrospective-sprint-N.md

Frequently Asked Questions about retrospective

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

FAQPage Schema

How do I facilitate a structured sprint retrospective for continuous improvement?▼

A sprint retrospective is needed at the end of every sprint, after major incidents, or when teams feel stuck, to collect feedback, review metrics, and plan concrete process improvements.

How do I run a retrospective that turns sprint metrics into concrete action items?▼

You run a retrospective by feeding sprint data such as metrics, completed tasks, and blocker logs into the skill, which then processes the inputs to generate a standardized document with goals and action items.

What is the best way to ensure our agile retrospective produces traceable improvement plans?▼

The best way to ensure traceable plans is to use a structured retrospective process that outputs a standardized document at .araya/plan/spec/retrospective-sprint-N.md, containing committed goals, metrics, and action items.

Can I use this retrospective skill for post-incident reviews instead of just regular sprint meetings?▼

Yes, you can use this retrospective skill for post-incident reviews, as it applies time-boxed, blameless reflection after incidents to identify learnings and commit to concrete process improvements.

Do I need to gather specific sprint data before starting the retrospective meeting?▼

Yes, you need to gather sprint data such as metrics, completed tasks, blocker logs, and team feedback beforehand to run the three acts and produce the final retrospective document.