retrospective
Skill0 starsChanged yesterdayMITView on GitHub
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".
73 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- andymai/skillstheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- sbfnk/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use dev-story, team-level and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkilldev-story
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.
Also in 12 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 12 projects that use this
- CoralGameSkill
team-narrative
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
Also in 12 projects that use this
- lilangMaxSkill
create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
- +7 more from lilangMax
- +1 more from CoralGame
Other versions73 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 73
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- alibaba/MNN★ 16ksame name
- glebis/claude-skills★ 410same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- blacklanternsecurity/red-run★ 296same name
- striderZA/OpenCodeGameStudios★ 118same name
- The01Geek/prflow★ 99same name
- PAIR-code/deliberate-lab★ 97same name
- AsiaOstrich/universal-dev-standards★ 84same name
- tranhieutt/software_development_department★ 71same name
63 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- decision-makingSkill
- delegation-briefSkill
- meeting-toolkitSkill
- project-budgetSkill
- project-charterSkill
- project-recoverySkill
- project-scheduleSkill
- responsibility-matrixSkill
- risk-registerSkill
- scope-changeSkill
- stakeholder-mapSkill
- status-updateSkill
- vendor-selectionSkill
- weekly-reviewSkill
- work-breakdownSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 62 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
When the same problems come back from one project to the next.
- Very specific: line 23
Not to rescue a project that is still running late: use project-recovery.
“Common” is measured: kept by at least 6 in 10 of the 62 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- The plan, the final dates and costs, the status updates.
- The people involved, and their perspectives.
- What was promised to clients, partners or family.
Method
- Set the stage: the goal is to learn, not to blame. Assume that everyone did their best with what they knew at the time.
- Gather the facts: a timeline of key events, planned versus actual (dates, budget, scope), and what each person noticed.
- 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.
- 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.
- 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.
- Share the lessons where the next project will find them.
Output
### Retrospective: <project or phase> (<date>)
Planned vs actual: dates … | budget … | scope …
Timeline: …
Worked well: … | Did not work: …
Causes: …
| Change | Owner | By | How we check |
|---|---|---|---|
### Closure checklist
Deliverables accepted | Handover done | Documents archived | Invoices settled | Thanks sentQuality bar
- Facts and the timeline come before opinions.
- Causes are dug into, and nobody is blamed.
- Two or three changes with owners and dates, not a long wish list.
- The project is formally closed: handover, documents, invoices, thanks.
- Written in the user's language, with the terms below.
Terminology
| English | Français | Español |
| Retrospective | Rétrospective | Retrospectiva |
| Lessons learned | Retour d'expérience, leçons apprises | Lecciones aprendidas |
| Root cause | Cause racine | Causa raíz |
| Blameless | Sans recherche de coupable | Sin culpables |
| Project closure | Clôture du projet | Cierre del proyecto |
| Handover | Passation | Traspaso |
Sources
- Derby, E., & Larsen, D. (2006). Agile Retrospectives: Making Good Teams Great. Pragmatic Bookshelf.
- Kerth, N. L. (2001). Project Retrospectives: A Handbook for Team Reviews. Dorset House.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.