skills.rest
alunadev
alunadevCOMMUNITY
Explore all skills by this author →
Website𝕏@adrianlunadiazGitHub

retro

Facilitate structured sprint retrospectives with Start/Stop/Continue, 4Ls, or Sailboat formats.

3|Updated Jan 20, 2026
Search Tags:#retrospective#continuous improvement#team dynamics#lessons learned#action items#sprint review
One-click install
npx skills add https://github.com/alunadev/ald-skills --skill retro-alunadev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/alunadev/ald-skills/tree/main/skills/retro
Command: npx skills add https://github.com/alunadev/ald-skills --skill retro-alunadev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms raw feedback from team retrospectives into concrete, prioritized action items, ensuring that lessons learned lead to tangible improvements in the next sprint or project phase.

Core Features & Use Cases

  • Multiple Retrospective Formats: Supports Start/Stop/Continue, 4Ls, and Sailboat methods to suit different team needs and maturity levels.
  • Action Item Prioritization: Focuses on generating 2-3 specific, actionable, and owned items based on root cause analysis.
  • Continuous Improvement Tracking: Includes a mechanism to review and status action items from previous retrospectives.
  • Use Case: After a challenging sprint, use the 'retro' skill to facilitate a discussion, identify key blockers, and generate clear action items like "Assign an owner to monitor external API status daily" to prevent future delays.

Quick Start

Facilitate a sprint retrospective using the Start/Stop/Continue format and define 2-3 action items.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I facilitate a sprint retrospective that generates actionable improvements?▼

Facilitate a structured sprint retrospective using formats like Start/Stop/Continue or 4Ls to analyze root causes and generate 2-3 specific, owned, and time-bound action items for continuous team development.

What is the best way to track action items from previous sprint reviews for accountability?▼

Track previous action items by using a continuous improvement mechanism that reviews and checks the status of past retrospective outputs, ensuring team accountability before starting a new sprint review.

When should I use the Sailboat retrospective format instead of 4Ls for team dynamics?▼

Use the Sailboat retrospective format to visually identify blockers and drivers impacting team dynamics, whereas 4Ls categorize feedback into Liked, Learned, Lacked, and Longed for to structure lessons learned.

Can I prioritize lessons learned to prevent future project delays after a challenging sprint?▼

Yes, prioritize lessons learned by conducting root cause analysis on raw feedback to define specific action items, such as assigning an owner to monitor external API status daily, preventing future delays.

Does this continuous improvement process work for teams needing customized retrospective formats?▼

Yes, it supports customizable retrospective formats including Start/Stop/Continue, 4Ls, and Sailboat, allowing you to adapt the continuous improvement process to different team needs and maturity levels.

Related Skills

Explore More Product & Management Skills→
bowiemaxbowiemax

retro

Facilitate structured sprint retrospectives and generate prioritized action items.

Community
Intermediate
pranav8494pranav8494
7

project-manager

Plan sprints, track dependencies, and produce RAG-flagged delivery artifacts.

Community
Intermediate
staticWagomUstaticWagomU
6

scrum-event-sprint-retrospective

Guide teams through structured sprint retrospectives to surface actionable improvements.

Community
Intermediate
MazenMradMazenMrad
1

gds-retrospective

Analyze epic execution data to extract lessons and track action items.

Community
Advanced