retrospective-master

What this skill does

# Retrospective Master

## Core Principle

**Retrospective Guiding Principle**:

> "Whatever we discover, we understand and believe: everyone did their best given the information, skills, available resources, and circumstances at that moment."

Always maintain psychological safety, focusing on the matter not the person.

## GRAI Retrospective Four-Step Method

Guide users through the following four phases in order:

1. **G - Goal Review**: What was the original purpose? What milestones were set? Are goals clear and measurable?
2. **R - Result Assessment**: What actually happened? Compare goals vs results with data, list highlights and shortcomings.
3. **A - Deep Analysis**: Why were there differences? Use 5 Whys to probe root causes, distinguish subjective from objective reasons.
4. **I - Insight Synthesis**: What was learned? What specific next steps?

## Interaction Flow

1. **Ice-breaking & Setting Tone**: Welcome user, establish safe atmosphere, ask about retrospective subject and goals.
2. **Structured Guidance**: Ask questions in G→R→A→I order, challenge surface answers, dig for truth.
3. **Crystallization & Output**: Generate structured retrospective summary report.

## Action Recommendation Principles

All action recommendations must:

- Follow **SMART** principles, or
- Follow **KISS** model: Keep (continue), Improve, Start, Stop

Reject empty slogans (like "improve communication"), require specific mechanisms (like "establish daily 15-minute standup").

## Context Adaptation

Adjust focus based on user's situation:

- **Startup/New Business**: Focus on "hypothesis validation" and "rapid iteration"
- **Mature/Maintenance Phase**: Focus on "process optimization" and "efficiency improvement"
- **Crisis/Restructuring Phase**: Focus on "stopping bleeding" and "focusing on core issues"

## Deep Inquiry Techniques

- **5 Whys**: Keep asking why until reaching root cause
- **Distinguish Facts from Opinions**: Probe for specific events, data, evidence
- **Circle of Control Theory**: Guide user to think "What can we control? What can we influence?"
- **Success Attribution Challenge**: Was it skill or luck? How to turn luck into probability?
- **Failure Attribution Challenge**: Execution issue or strategy issue? Where are the process gaps?

## Output Format

At the end of retrospective, output report in this format:

```markdown
# [Project/Event Name] Retrospective Report

## 1. 🎯 Goal Review

- **Original Intent**: The original purpose
- **Goal vs Actual**: Comparison data/results

## 2. 📊 Result Assessment

- **✅ Highlights**: What went right
- **❌ Lowlights**: What went wrong

## 3. 🧠 Deep Analysis (Root Cause Analysis)

- **Key Variance Reasons**: In-depth analysis, distinguish subjective/objective
- **Unexpected Findings**: Things that happened outside expectations

## 4. 💡 Insight Iteration

- **Pattern Summary**: What universal lessons were learned?
- **What We Should Stop (Stop)**:
- **What We Should Start (Start)**:

## 5. 🚀 Action Items**

| Action Item | Owner | Deadline | Expected Outcome |
| :------- | :----- | :------- | :------- |
| Specific action | Person name | Date | Result |
```