retrospective-master
Professional retrospective coach based on the GRAI model (Goal-Result-Analysis-Insight) to guide users through structured retrospectives. Transform experiences into lessons, and lessons into capabilities. Use when: (1) Systematic review needed after project/event completion, (2) Learning from failures, (3) Summarizing and replicating success experiences, (4) Creating improvement action plans.
- Installs
- 50
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/hexbee/hello-skills --skill retrospective-master- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads retrospective-master automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
- G - Goal Review: What was the original purpose? What milestones were set? Are goals clear and measurable?
- R - Result Assessment: What actually happened? Compare goals vs results with data, list highlights and shortcomings.
- A - Deep Analysis: Why were there differences? Use 5 Whys to probe root causes, distinguish subjective from objective reasons.
- I - Insight Synthesis: What was learned? What specific next steps?
Interaction Flow
- Ice-breaking & Setting Tone: Welcome user, establish safe atmosphere, ask about retrospective subject and goals.
- Structured Guidance: Ask questions in G→R→A→I order, challenge surface answers, dig for truth.
- 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:
# [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 |
FAQ
What does the retrospective-master skill do?
Professional retrospective coach based on the GRAI model (Goal-Result-Analysis-Insight) to guide users through structured retrospectives. Transform experiences into lessons, and lessons into capabilities. Use when: (1) Systematic review needed after project/event completion, (2) Learning from failures, (3) Summarizing and replicating success experiences, (4) Creating improvement action plans.
How do I install retrospective-master?
Run npx skills add https://github.com/hexbee/hello-skills --skill retrospective-master in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/retrospective-master/ (personal) or .claude/skills/retrospective-master/ (project).
Which AI agents can use retrospective-master?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is retrospective-master safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains retrospective-master?
It is published by hexbee in hexbee/hello-skills. It has 50 recorded installs.
More from hexbee/hello-skills
deep-productivity
hexbee/hello-skills
Master deep work productivity through the three types of work framework (Building, Maintenance, Recovery). Use when user needs to: (1) Build a sustainable deep work routine with just 1 hour/day, (2) Create vision/anti-vision for life direction, (3) Structure goals using the 10-year → 1-year → 1-month → 1-week hierarchy, (4) Apply project-based learning to bridge skill gaps, (5) Identify lever-moving tasks that actually progress goals, (6) Balance focus work with necessary recovery for creativity.
mungers-lattice
hexbee/hello-skills
Multidisciplinary analytical engine using Charlie Munger's latticework of mental models. Applies cross-disciplinary thinking (math, physics, biology, psychology, economics) to dissect life and business decisions. Use when user presents a decision problem, investment question, or complex analysis request requiring deep rational analysis.
cross-domain-thinking-toolbox
hexbee/hello-skills
Open the skill to read its SKILL.md instructions.
learning-first-principles
hexbee/hello-skills
A cognitive framework based on learning first principles, providing learning method diagnosis, efficiency assessment, and optimization advice. Use when: (1) Diagnosing if current learning methods align with first principles, (2) Evaluating learning plan efficiency and time investment, (3) Analyzing learning behavior problems and providing improvement suggestions, (4) Determining if learning content is worth the time investment. Core principle chain: Self-learning → Induction → Self-output → Expression restructuring → Logical understanding → Practice.
instreet-operator
hexbee/hello-skills
Deprecated: this skill has been deprecated. Use this when working with InStreet forum or Playground flows. It restores account state from /.instreet, can auto-register when no local account exists, and routes all InStreet API requests through the bundled Python client. It has first-class commands for forum, groups, literary, arena, oracle, and games workflows, with raw api fallback for long-tail endpoints.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.