skills.rest
moonzff
moonzffCOMMUNITY
Explore all skills by this author →
GitHub

retro

Facilitate structured sprint retrospectives with themed feedback and prioritized action items.

1|Updated May 6, 2026
Search Tags:#retrospective#agile#action items#scrum#facilitation#sprint#team feedback
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill retro-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/moonzff/Codex_up/tree/main/skills/docs-meetings-writing/retro
Command: npx skills add https://github.com/moonzff/Codex_up --skill retro-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often finish sprints without a structured way to reflect on what worked, what failed, and what to change, leaving recurring problems unaddressed and improvement ideas untracked. ## Core Features & Use Cases - Multiple Retro Formats: Choose from Start/Stop/Continue, 4Ls (Liked/Learned/Lacked/Longed For), or Sailboat formats based on team context. - Feedback Theming: Group raw feedback from sticky notes, surveys, or chat messages into themes with sentiment analysis. - Prioritized Action Items: Generate 2-3 specific, assignable, measurable action items with owners, deadlines, and success metrics. - Use Case: After a two-week sprint where the team missed its velocity target, paste the sprint metrics and team feedback to receive a structured retro summary with themed insights and carry-over tracking from the previous retrospective. ## Quick Start Run a sprint retrospective using the attached team feedback and velocity data, and produce a summary with prioritized action items.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I run a sprint retrospective with my team?▼

Choose a retro format such as Start/Stop/Continue, 4Ls, or Sailboat, then gather team feedback and group it into themes. Analyze sprint goal achievement and velocity, then produce 2-3 prioritized action items with owners and deadlines.

What retrospective format should I use for my team?▼

Start/Stop/Continue works for general process improvement, 4Ls suits learning-focused teams, and Sailboat fits goal-oriented discussions about risks and drivers. Pick based on the team's current context or let participants choose.

How do I turn raw team feedback into retro action items?▼

Group similar feedback items into themes, identify the most frequently mentioned topics, and note sentiment patterns. Convert the top themes into 2-3 specific, assignable, measurable action items with owners and success metrics.

How many action items should a retrospective produce?▼

Limit action items to 2-3 per retrospective, since more items rarely get completed. Each item must be specific, assignable to an owner, and measurable with a clear success metric and deadline.

Can I track action items from previous retrospectives?▼

Yes, the retro summary includes a carry-over section that references previous action items and marks their status as Done, In Progress, or Not Started. This keeps accountability visible across sprints.

Related Skills

Explore More Product & Management Skills→
mahg-esmahg-es
3

retrospective

Facilitate structured sprint retrospectives and generate action plans.

Official
Intermediate
openyakopenyak
704

call-summary

Extract decisions, action items, and owners from call notes or transcripts.

Official
Intermediate
Lobbi-DocsLobbi-Docs
18

scrum

Plan sprints, coordinate standups, and manage backlogs for Agile teams.

Official
Basic
aaronjmarsaaronjmars
714

skill-health

Audits scheduled skill runs, files failure issues, and ranks fleet-wide analytics.

Community
Advanced