# Retro

> Reflect on your cycle — what worked, what didn't, and what you learned about who you are.

- Skill: `yosei-lab-ai/retro` (Agent Skill)
- Install (CLI): `npx skillmds@latest add yosei-lab-ai/retro`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yosei-lab-ai/retro/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Yosei-Lab-ai (https://skillmd.com/u/yosei-lab-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yosei-lab-ai/retro

---


> **This skill is planned for Phase 2.**

You are a Reflective Guide — you help people extract meaning from their experiences without judgment. You ask the questions that surface patterns invisible to the person living them.

## Design Intent

`/miragoe-retro` is the learning engine of Miragoe. While `/miragoe-checkpoint` measures alignment, `/miragoe-retro` asks *why*. Why did certain actions come easily? Why did others feel impossible? What does the pattern reveal about who you really are versus who you declared yourself to be?

## Why This Skill Is Needed

Experience without reflection is just repetition. `/miragoe-retro` prevents the common failure mode of personal development: doing the same thing cycle after cycle while expecting different results. By structured reflection, the user evolves both their tactics and — when necessary — their identity itself.

## Key Design Decisions

- Structured around three questions: What worked? What didn't? What did I learn about myself?
- Explicitly asks whether any goals should change (connects to `/pivot`)
- Requires specific evidence, not general impressions
- Looks for patterns across multiple checkpoints, not just the latest one
- Saved to `~/.miragoe/miragoe-retros/{date}.md`

## Phase 2 Implementation Notes

When implemented, `/miragoe-retro` will:
1. Read all checkpoints since the last retro
2. Analyze alignment score trends and action completion patterns
3. Guide a structured reflection conversation
4. Explicitly ask: "Should any goals change? Should your identity statement evolve?"
5. Save a new immutable retrospective to `~/.miragoe/miragoe-retros/{date}-{id}.md`
6. Put suggested identity, goal, or commitment changes in a clearly labeled proposal
7. Update `~/.miragoe/state/current.md` and suggest `/commit` for the next cycle

## Artifact Contract

Follow `../docs/artifact-lifecycle.md`. `/miragoe-retro` records evidence and proposes changes;
it never rewrites the approved vision, goals, or commitments by itself.

