elon-retro

Guide teams through structured retrospectives to analyze outcomes and identify root causes.

33|3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/justinz183/elon-skill --skill elon-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elon-retro
Source: https://github.com/justinz183/elon-skill/tree/main/retro
Command: npx skills add https://github.com/justinz183/elon-skill --skill elon-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams conduct effective retrospectives to extract maximum learning, update mental models, and reduce errors post-project completion.

Core Features & Use Cases

  • Structured Retrospective: Guides the user through a comprehensive process to analyze past outcomes.
  • Root Cause Analysis: Encourages a deep dive into understanding the underlying reasons behind successes and failures.
  • Continuous Improvement: Facilitates the updating of mental models and the planning of future experiments based on learnings.
  • Use Case: After a project launch, use this Skill to review the outcomes, identify areas for improvement, and adjust strategies for the next iteration.

Quick Start

Run a retro for the 'Project X' by executing /elon-retro.

Frequently Asked Questions about elon-retro

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

FAQPage Schema
How do I conduct a structured retrospective for project review?

To conduct a structured retrospective, you guide the team through analyzing project outcomes, identifying root causes, and updating mental models to extract maximum learning. This structured process reduces errors and improves future performance.

What is root cause analysis in a team retrospective?

Root cause analysis in a team retrospective is a process to deeply investigate the underlying reasons behind project successes and failures. It encourages critical thinking to move beyond surface-level issues and identify true drivers of outcomes.

When do I need to run a retrospective for continuous improvement?

You need to run a retrospective for continuous improvement after a project launch or completion. It helps review outcomes, identify areas for improvement, and adjust strategies to plan future experiments based on learnings.

How do retrospectives update mental models for team learning?

Retrospectives update mental models for team learning by facilitating a comprehensive review of past outcomes and root causes. This structured analysis challenges existing assumptions and adjusts strategies for the next iteration.

Do I need critical thinking skills to facilitate a project retrospective?

Yes, you need critical thinking and analysis skills to facilitate a project retrospective effectively. These skills are required to guide teams through root cause analysis and update mental models during continuous improvement initiatives.