retro

Facilitate structured sprint retrospectives and produce prioritized action items with owners and deadlines.

2|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/skytiger6724/qwen-skills --skill retro-skytiger6724
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/skytiger6724/qwen-skills/tree/main/retro
Command: npx skills add https://github.com/skytiger6724/qwen-skills --skill retro-skytiger6724

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured sprint retrospectives often end without clear insights, action items, or accountability, leaving teams unable to improve effectively.

Core Features & Use Cases

  • Guide Format Selection: Recommends Start/Stop/Continue, 4Ls, or Sailboat structures based on sprint context, available data, and team preference.
  • Feedback & Performance Analysis: Synthesizes sprint goals, goal completion, velocity vs. commitment, blockers, collaboration patterns, and raw feedback so every angle is captured.
  • Action Planning: Crafts 2-3 prioritized, measurable action items with owners, deadlines, and success metrics while checking progress on previous retro commitments.

Quick Start

Facilitate a Start/Stop/Continue retrospective for the latest sprint, summarize the outcomes, and produce 2-3 measurable action items with owners and dates.

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 that produces actionable improvements?

Run a sprint retrospective by synthesizing sprint goals, velocity data, and feedback to surface lessons learned. The process generates 2-3 prioritized action items with assigned owners, deadlines, and success metrics to ensure measurable improvements.

What is the best way to track carry-over action items from previous retros?

Track carry-over action items by reviewing previous retro commitments during the current feedback synthesis. This checks progress on prior action items while organizing new insights, blockers, and collaboration patterns into prioritized tasks with clear ownership and deadlines.

Which retrospective format should my agile team use for sprint review?

Choose a retrospective format based on sprint context, available data, and team preference. Recommended structures include Start/Stop/Continue, 4Ls, or Sailboat, each tailored to organize insights and performance analysis for different agile team dynamics.

Can I analyze velocity vs commitment data during a team retro?

Yes, you can analyze velocity vs commitment data during a team retro. The retrospective synthesizes goal completion metrics, velocity data, and collaboration signals alongside raw feedback to capture every angle of sprint performance and identify blockers.

Why do structured retrospectives fail to generate measurable improvements?

Structured retrospectives fail when they end without clear insights, action items, or accountability. Effective retrospectives solve this by synthesizing performance data into prioritized, measurable action items with owners, deadlines, and success metrics for continuous improvement.

Does this retrospective tool work for agile teams needing performance analysis?

Yes, this retrospective tool works for agile teams needing performance analysis. It synthesizes sprint goals, blockers, collaboration patterns, and velocity data to produce prioritized action items with success metrics, ensuring comprehensive feedback synthesis and accountability.