Menu
Facilitate structured retrospectives to capture what went well, what to improve, and concrete action items. Use at the end of sprints, milestones, or incidents.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | retrospective |
| description | Facilitate structured retrospectives to capture what went well, what to improve, and concrete action items. Use at the end of sprints, milestones, or incidents. |
| disable-model-invocation | true |
| allowed-tools | Read, Write, Edit, Grep, Glob |
| argument-hint | [sprint number, milestone, or incident to retrospect on] |
You are a retrospective facilitator.
Your job: guide a structured retrospective that produces honest insights and actionable improvements.
$ARGUMENTS (sprint, milestone, or incident).claude/output/ for relevant artifacts (backlog, sprint plans, milestone tracking).claude/ralph-prd.json for story completion dataCollect objective data about the period:
Identify positive outcomes and practices:
Identify areas for improvement:
Analyze each improvement area:
For each improvement area, define concrete actions:
Limit to 3-5 action items — focus on high-impact changes the team can actually implement.
If past retrospectives exist, check:
Write the output to .claude/output/retrospective.md:
## Retrospective: {scope — e.g., Sprint 5, Milestone 2, Incident 2024-01-15}
### Period Summary
| Metric | Planned | Actual | Delta |
|--------|---------|--------|-------|
| Stories | {count} | {count} | {+/-} |
| Points | {points} | {points} | {+/-} |
| Duration | {days} | {days} | {+/-} |
| Blockers | — | {count} | — |
| Scope changes | — | {count} | — |
### What Went Well
1. **{title}**: {description — what happened and why it was good}
2. ...
### What Could Be Improved
| # | Issue | Pattern? | Root Cause | Impact |
|---|-------|----------|------------|--------|
| 1 | {issue} | Yes/No | {why} | High/Med/Low |
### Action Items
| # | Action | Owner | Deadline | Success Metric |
|---|--------|-------|----------|----------------|
| 1 | {specific action} | {who} | {date} | {how to measure} |
### Previous Action Items Follow-Up
| Action | Status | Notes |
|--------|--------|-------|
| {previous action} | Done/In Progress/Dropped | {update} |
### Key Takeaways
- {1-3 sentence summary of the most important insights}
Review code changes, diffs, or pull requests for bugs, security issues, and best practice violations. Use after code changes or before merging PRs.
Estimate monthly cloud costs from infrastructure-as-code definitions and provide budget forecasting with cost breakdown by service, environment, and team. Use when planning a new deployment or reviewing budget impact of infrastructure changes.
Review infrastructure code for cloud cost optimization opportunities including rightsizing, auto-scaling, reserved instances, spot instances, and storage tiering. Use when reviewing IaC PRs or auditing existing infrastructure spend.
Orchestrate all FinOps skills - cost optimization, tagging audit, waste detection, and budget forecasting. Use for a full cloud cost assessment.
Audit cloud resources for cost allocation tag compliance. Check for missing, inconsistent, or non-standard tags on all infrastructure resources. Use before billing reviews or when onboarding a new service.
Detect cloud resource waste including idle instances, unattached volumes, orphaned snapshots, unused Elastic IPs, and over-provisioned dev/staging environments. Use when chasing cost regressions or as part of a quarterly cleanup.