← ClaudeAtlas

retrospectivelisted

Learn from a project or a phase without blaming anyone: gather the facts and a timeline, find what went well and what did not, dig into the causes, and turn them into a few concrete changes with owners, then close the project properly (handover, documents, thanks). Use at the end of a project, after a milestone, after a failure or an incident, or when the same problems keep coming back. Triggers: "retrospective", "lessons learned", "post-mortem", "what went wrong", "project closure", "retour d'expérience", "bilan de projet", "leçons apprises", "clôture du projet", "retrospectiva", "lecciones aprendidas", "cierre del proyecto".
teodstr/workbench · ★ 0 · Testing & QA · score 66
Install: claude install-skill teodstr/workbench
# Retrospective A retrospective is only useful if it changes how the next project runs. This skill follows the structure Derby and Larsen describe (set the stage, gather data, generate insights, decide what to do, close) and ends with a few changes that someone owns. ## When to use - At the end of a project, after each phase of a long one, or after an incident. - When the same problems come back from one project to the next. - Not to rescue a project that is still running late: use `project-recovery`. ## Inputs 1. The plan, the final dates and costs, the status updates. 2. The people involved, and their perspectives. 3. What was promised to clients, partners or family. ## Method 1. **Set the stage**: the goal is to learn, not to blame. Assume that everyone did their best with what they knew at the time. 2. **Gather the facts**: a timeline of key events, planned versus actual (dates, budget, scope), and what each person noticed. 3. **Find what worked and what did not**, then dig into the causes of the main problems by asking "why" several times until the cause is something that can be changed. 4. **Decide on a few changes**: two or three, each with an owner and a date, and the way to check next time that it helped. 5. **Close the project**: confirm the deliverables are accepted, hand over to whoever maintains the result, archive the documents and the decision log, settle the last invoices, thank the people involved. 6. **Share the lessons** where the next project will f