retro
Skill11 starsChanged 11 days agoMITView on GitHub
Post-cycle review — extract lessons, calibrate estimates, improve processes, compact memory, and update team knowledge. Consult @ml-ai-engineer where eval harnesses, benchmarks, or biomarker pipelines are under review. Use when the user says "run a retro", "what did we learn this cycle", "calibrate our estimates", or invokes /retro after a cycle or launch.
194 other projects use a version of this.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- bmcszk/agent-skillstheir own version, first seen Nov 16, 2026
- Gord1y/countersign-skillstheir own version, first seen Nov 16, 2026
- devdeepjs/kobayashi-marutheir own version, first seen Nov 16, 2026
- qelphybox/tg-mcptheir own version, first seen Nov 16, 2026
- icetomoyo/CodingSkillstheir own version, first seen Nov 16, 2026
Used with
Projects with it also use plan-tune, ios-clean 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.
ShreyRaviSkillplan-tune
Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.
Also in 9 projects that use this
Saqlain-811Skillios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
Saqlain-811Skillios-fix
Autonomous iOS bug fixer. (gstack)
Also in 5 projects that use this
seek888Skillpair-agent
Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".
Also in 11 projects that use this
ShreyRaviSkilllanding-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 8 projects that use this
timurgaleevSkilldocument-generate
Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.
Also in 7 projects that use this
- +1 more from Saqlain-811
- +2 more from ShreyRavi
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 194
- mattpocock/skills★ 325ksame name
- garrytan/gstack★ 142ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 5ksame name
- bergside/awesome-design-skills★ 2.9ksame name
- MiniMax-AI/minimax-code★ 2.2ksame name
- DenchHQ/DenchClaw★ 1.7ksame name
- DenchHQ/ironclaw★ 1.7ksame name
184 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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-dataSkill
- brainstormingSkill
- craft-lessonSkill
- create-agentSkill
- create-skillSkill
- customize-agentSkill
- customize-skillSkill
- designSkill
- deslopSkill
- developSkill
- discovery-reportSkill
- elicitationSkill
- empathy-mapSkill
- explore-ideaSkill
- grill-meSkill
- help-meSkill
- humanizeSkill
- incidentSkill
- iterateSkill
- journey-mapSkill
- jtbdSkill
- kanbanSkill
- launchSkill
- legal-safety-auditSkill
- maintenance-executeSkill
- maintenance-planSkill
- memorySkill
- motionSkill
- phaseSkill
- planSkill
- research-planSkill
- reviewSkill
- root-causeSkill
- round-tableSkill
- shape-upSkill
- shut-upSkill
- statusSkill
- teach-meSkill
- testSkill
- unpack-problemSkill
- validate-ideaSkill
- validation-patternsSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Follow the step sequence exactly.
- Distinctive: line 20
After completing a development cycle or shipping a launch
- Distinctive: line 21
After resolving an incident
- Very specific: line 23
After 5 iteration cycles (mandatory trigger) — recorded as lastRetroCycle in artifacts/output/07-iteration/iteration-state.md, which is …
- Very specific: line 30
Read stepsCompleted array from artifacts/output/09-retro/retro-state.md (or start at []).
- Distinctive: line 57
At completion (step-05): Write session summary — mandatory:
- Very specific: line 68
All five steps in stepsCompleted, no gaps
“Common” is measured: kept by at least 6 in 10 of the 170 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
Retro — Multi-Step Workflow
<!-- router-skill -->This skill runs in sequential steps. Each step is a self-contained file with its own halt conditions. Load one at a time.
Harness adherence (non-negotiable)
- Follow the step sequence exactly. Do NOT skip steps or reorder them.
- Memory compaction runs automatically at step 5 — the swarm does NOT block on human input.
- Each step file is a contract. Read it fully before executing.
When to invoke
- After completing a development cycle or shipping a launch
- After resolving an incident
- At regular intervals (every 2-4 weeks)
- After 5 iteration cycles (mandatory trigger) — recorded as
lastRetroCycleinartifacts/output/07-iteration/iteration-state.md, which is whatcycle_state_check.js --kind iteratechecks before a sixth cycle can start
Prerequisites
- Completed phase artifact (launch-log.md, incident-postmortem.md, or iteration report)
artifacts/memory/directory with active entries
Step loader
- Read
stepsCompletedarray fromartifacts/output/09-retro/retro-state.md(or start at []). - Compute next step = first step NOT in
stepsCompleted. - Load
steps/step-{NN}-*.md. - Execute. On completion, append NN to
stepsCompletedand re-invoke loader.
Step sequence
- Hot Paths →
steps/step-01-hot-paths.md - Pattern Scan →
steps/step-02-pattern-scan.md - Instinct Scan →
steps/step-03-instinct-scan.md - Write Digest →
steps/step-04-write-digest.md - Compact →
steps/step-05-compact.md
Halt conditions
- Memory integrity check fails (
memory_check.js checkreturns non-zero) - Pattern scan finds unresolved security or data-loss patterns (escalate to
@tech-lead) - Compaction would archive entries younger than 7 days (skip compaction, report)
State machine integration
At start: run node .agents/scripts/orchestrator_state.js status
At end: run node .agents/scripts/orchestrator_state.js complete --agent memory-controller --artifact 09-retro/retro-digest.md
Memory integration
At start (step-01): Load full memory context before hot-path scan:
@memory-controller load memory-controller [retro — post-cycle review]At completion (step-05): Write session summary — mandatory:
@memory-controller session-write [agent: @memory-controller]
Worked on: Post-cycle retro — {cycle or sprint description}
Decisions: {key process improvements, estimate calibrations, compacted entries}
Next step: {next development cycle, or launch if shipping}
Blockers: {unresolved patterns or "none"}Done when
cycle_state_check.js check --kind retroexits 0 — the three bullets below are what it verifies- All five steps in
stepsCompleted, no gaps retro-digest.mdwritten toartifacts/output/09-retro/with real substance- Memory compacted (or skip recorded)
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.

