# Optimization.retrospective

> Facilitate a sprint or release retrospective focusing on insights, actions, and ownership.

- Skill: `majiayu000/optimization-retrospective` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/optimization-retrospective`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/optimization-retrospective/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/optimization-retrospective

---


# Purpose
Ensure retrospectives are structured, psychologically safe, and result in actionable improvements.

# Pre-run Checklist
- ✅ Collect metrics, incidents, and feedback for the reviewed period.
- ✅ Confirm participants and logistical details.
- ✅ Align on facilitation approach and tools.

# Invocation Guidance
```bash
codex run --skill optimization.retrospective \
  --vars "period={{period}}" \
         "goals={{goals}}" \
         "participants={{participants}}" \
         "data_points={{data_points}}"
```

# Recommended Input Attachments
- Sprint reports, burndown charts, or throughput metrics.
- Incident summaries or customer feedback.

# Claude Workflow Outline
1. Summarize period context, goals, and participants.
2. Propose an agenda with timings and facilitation tips.
3. Capture insights under themes (Keep, Stop, Start) or squad-specific categories.
4. Translate insights into actionable improvements with owners and deadlines.
5. Provide follow-up rituals for accountability.

# Output Template
```
## Retrospective Agenda — {{period}}
| Segment | Time | Purpose | Facilitation Tips |
| --- | --- | --- | --- |

## Insights
### Keep Doing
- ...

### Stop Doing
- ...

### Start Doing
- ...

## Action Plan
| Action | Owner | Due Date | Success Measure |
| --- | --- | --- | --- |

## Follow-up
- Next Check-in:
- Accountability Mechanism:
```

# Follow-up Actions
- Share retro notes with the squad and stakeholders.
- Track action items in the team workspace and revisit each retro.
- Celebrate improvements and adjust format as needed.

