retrospective
Skill0 starsChanged 3 months agoMITView on GitHub
Review what worked, what blocked progress, and what must change next.
69 other projects use a version of this.
Adopted by
Most recently taken up by
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- sbfnk/skillstheir own version, first seen Nov 8, 2026
- AndyB840506/skillstheir own version, first seen Nov 8, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- AsiaOstrich/EngramGraphtheir own version, first seen Nov 8, 2026
- simonasrazm/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 versions69 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 69
- Donchitos/Claude-Code-Game-Studios★ 27ksame 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
59 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 repository30 other files it gives its agents.
- auditSkill
- bootstrap-agent-contextSkill
- buildSkill
- closeSkill
- decision-logSkill
- feature-trackerSkill
- handoffSkill
- health-checkSkill
- idea-to-briefSkill
- live-state-preflightSkill
- portfolio-reviewSkill
- pre-commit-reviewSkill
- resolveSkill
- session-summarySkill
- spec-packSkill
- stack-summarySkill
- strategizeSkill
- testSkill
- the-loop-autonomySkill
- the-loop-autoSkill
- the-loop-cloudSkill
- the-loop-controlSkill
- the-loop-doctorSkill
- the-loop-endlessSkill
- the-loop-parallelSkill
- the-loop-setupSkill
- the-loop-skill-creatorSkill
- the-loopSkill
- the-loop-skill-plannerSkill
- the-loop-watchSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 58 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use after bounded slices complete or when recurrent failures recur.
- Distinctive: line 29
Create concise follow-up actions with owners and evidence requirements.
- Distinctive: line 31
Avoid inventing conclusions not supported by logs.
- Distinctive: line 40
Stop with a precise error for missing authority, expired lease, namespace mismatch, unsafe proof, private data exposure, unknown …
“Common” is measured: kept by at least 6 in 10 of the 58 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
Review what worked, what blocked progress, and what must change next.
Use when
- Use after bounded slices complete or when recurrent failures recur.
Inputs
- Active run, objective, track, and authority context.
- Declared track boundaries and budget controls.
- Typed evidence references and required file paths.
Procedure
- Collect completed evidence, failures, and recurring anti-patterns.
- Assign likely root causes and confidence levels.
- Create concise follow-up actions with owners and evidence requirements.
- Persist learnings in approved non-sensitive format.
- Avoid inventing conclusions not supported by logs.
Output contract
- Deterministic status, evidence hash list, and explicit status transitions.
- Typed halt reason with exact next-step obligations when blocked.
Halt conditions
Stop with a precise error for missing authority, expired lease, namespace mismatch, unsafe proof, private data exposure, unknown capability, or unverified behavior claim.
Notes
Core execution does not require network access or the source checkout. Use the bundled fallback behavior when live capabilities are blocked.
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.