reflect-retrospective

Name: reflect-retrospective
Availability: InStock
Author: piercingxx

Generate structured retrospective and incident post-mortem outputs with action items.

1|Updated Jul 9, 2026

Search Tags:#root cause analysis #retrospective #post-mortem #lessons learned #action items #delivery improvement

Ready to run

npx skills add https://github.com/PiercingXX/xx-stack --skill reflect-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reflect-retrospective
Source: https://github.com/PiercingXX/xx-stack/tree/main/runtime/skills/reflect-retrospective
Command: npx skills add https://github.com/PiercingXX/xx-stack --skill reflect-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams move past vague impressions by structuring reflection into actionable lessons learned, reducing repeat failures and improving delivery quality on future work.

Core Features & Use Cases

Guided retrospective formats: Run a 30-minute quick retro or a 1–2 hour full retro with clear steps for strengths, difficulties, surprises, and follow-ups.
Incident-ready post-mortem structure: Capture timelines, perform root-cause analysis, document impact, and define immediate and preventive measures.
Action item rigor: Convert insights into specific, owned, and trackable next steps suitable for engineering, design, and delivery teams.

Quick Start

Use reflect-retrospective to plan a blame-free retro by asking the AI to generate a Quick Retro agenda and 3 specific action items for your last sprint.

Frequently Asked Questions about reflect-retrospective

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

FAQPage Schema

How do I run a blame-free retrospective for my team after a sprint?▼

A blame-free retrospective captures what went well, what was hard, and lessons learned to generate specific, owned action items. You can run a 30-minute quick retro or a 1-2 hour full retro with structured steps for strengths, difficulties, and follow-ups.

How do I write an incident post-mortem with root cause analysis?▼

An incident post-mortem captures timelines, performs root-cause analysis, documents impact, and defines immediate and preventive measures. It converts incident insights into specific, owned, and trackable next steps suitable for engineering teams.

What is the best way to turn project learnings into actionable follow-ups?▼

Turning project learnings into actionable follow-ups converts vague impressions into specific, owned, and trackable next steps. This structured reflection process reduces repeat failures and improves delivery quality on future work.

Can I use this retrospective format for both shipped projects and outages?▼

Yes, retrospective formats apply to shipped projects, completed delivery milestones, team learning sessions, features, regressions, and outages. They fulfill a facilitator-led workflow with blame-free guidance suitable for engineering, design, and delivery teams.

What is the difference between a quick retro and a full retro?▼

A quick retro is a 30-minute session, while a full retro takes 1-2 hours with clear steps for strengths, difficulties, surprises, and follow-ups. Both formats use output templates to convert insights into actionable, trackable next steps.