retrospective
Skill9 starsChanged 7 months agoMITView on GitHub
Sprint retrospective facilitation — what went well, what didn't, action items for next sprint.
72 other projects use a version of this.
Adopted by
Most recently taken up by
- andymai/claude-agent-teamtheir own version, first seen Nov 16, 2026
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- teodstr/workbenchtheir 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
- dzianisv/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use dev-story, team-level and 9 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
CoralGameSkillteam-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
lilangMaxSkillcreate-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
Other versions72 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 72
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- alibaba/MNN★ 17ksame name
- glebis/claude-skills★ 414same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- The01Geek/prflow★ 100same name
- PAIR-code/deliberate-lab★ 97same name
- AsiaOstrich/universal-dev-standards★ 84same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
62 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 repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 61 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Ask: "Which sprint are we retrospecting?"
- Very specific: line 14
Default: most recent sprint in production/sprints/
- Distinctive: line 25
Ask the user to reflect on:
- Very specific: line 96
Update production/decision-log.md with key learnings.
“Common” is measured: kept by at least 6 in 10 of the 61 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 — Sprint Retrospective
Delegate to: producer
Steps
1. Identify Sprint
Ask: "Which sprint are we retrospecting?"
- Default: most recent sprint in
production/sprints/
2. Load Sprint Data
Read:
- Sprint plan (original commitments)
- Milestone reviews (if this sprint spanned a milestone)
- Decision log entries from this sprint's timeframe
- Any bug reports filed
- Metrics if available (agent log, time tracking)
3. Facilitate Reflection
Ask the user to reflect on:
What went well?
- Features shipped as planned
- Good process moments
- Effective collaboration
- Technical wins
What didn't go well?
- Tasks that slipped
- Unexpected blockers
- Process friction
- Bugs that escaped to production
What should we try?
- New practices to experiment with
- Changes to existing process
- Tool improvements
- Agent delegation patterns that might help
What should we stop?
- Practices that aren't paying off
- Meetings or overhead that's not useful
- Tool usage that's hurting flow
4. Extract Action Items
For each "try" or "stop":
- Make it concrete and assignable
- Give it a target sprint
- Define success criteria
5. Generate Retro Document
# Retrospective: Sprint [N]
**Date**: YYYY-MM-DD
**Duration**: [start date] to [end date]
**Participants**: [user]
## Sprint Summary
- Committed: X tasks
- Completed: Y tasks
- Added mid-sprint: Z tasks
- Carried over: W tasks
## What Went Well 🟢
1. [Specific win]
2. [Specific win]
## What Didn't Go Well 🔴
1. [Specific issue]
2. [Specific issue]
## What to Try 🆕
1. [Concrete experiment]
2. [Concrete experiment]
## What to Stop 🛑
1. [Practice to drop]
## Action Items
- [ ] [Action item with owner and target sprint]
- [ ] [Action item with owner and target sprint]
## Key Learnings
- [Insight worth remembering]
- [Insight worth remembering]Output
Present the retro draft. On approval, save to production/sprints/sprint-<N>-retro.md.
Update production/decision-log.md with key learnings.
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.

