weekly-retro
Skill2 starsChanged 5 months agoMITView on GitHub
Weekly retro — reviews the week against active development objectives, surfaces patterns vs. prior weeks, and lands on one concrete development intention for next week. Run on Fridays.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- 0xUrsanomics/utopia-ostheir own version, first seen Nov 1, 2026
- JamsusMaximus/growth-agentstheir own version, first seen Oct 25, 2026
- jp-solumhealth/jpstacktheir own version, first seen Oct 14, 2026
- serejaris/ris-claude-codetheir own version, first seen Oct 9, 2026
- serejaris/personal-corp-ostheir own version, first seen Aug 6, 2026
- megandmartin/agent-skills-repotheir own version, first seen Jul 24, 2026
Used with
Projects with it also use idea.
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.
szweibelSkillidea
Generate a wide field of options when the user is brainstorming, exploring, expanding, or pressure-testing — not recommending or implementing
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- serejaris/personal-corp-os★ 244same name
- serejaris/ris-claude-code★ 243same name
- JamsusMaximus/growth-agents★ 21same name
- megandmartin/agent-skills-repo★ 4same name
- Joshua-Palamuttam/workbench-template★ 3same name
- 0xUrsanomics/utopia-os★ 2same name
- jp-solumhealth/jpstack★ 0same name
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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- control-plane/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- control-plane/CLAUDE.mdCLAUDE.md
- agentic-os-reference-syncSkill
- branch-cleanupSkill
- capture-triageSkill
- darwin-housekeepingSkill
- darwin-path-modeSkill
- decision-log-entrySkill
- eodSkill
- expert-interview-guideSkill
- feedback-intakeSkill
- harness-onboardingSkill
- ingest-contentSkill
- meeting-to-work-itemsSkill
- memory-consolidateSkill
- morning-briefSkill
- os-bootstrap-extendSkill
- os-bootstrapSkill
- pr-reviewSkill
- scheduleSkill
- spec-cross-checkSkill
- ux-critiqueSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
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 28
Don't lecture. Ask questions and listen.
- Very specific: line 36
Add strong moments (good or missed) to the evidence log in objectives.md
- Distinctive: line 44
Keep the file write quiet — don't narrate "now I am writing the file".
“Common” is measured: kept by at least 6 in 10 of the 6 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
Skill: weekly-retro
Purpose
Turn the week's actual behavior into compounding career development — so formal reviews are a compilation exercise, not an archaeology dig.
Steps
- Read silently
- This week's
control-plane/memory/daily/logs control-plane/memory/development/objectives.md— active objectives + evidence logs- Last 1-2 files in
control-plane/memory/development/retros/— cross-week patterns
- This week's
- Walk through the week conversationally (support-coach register, not work-advisor)
- What went well / what didn't — bring specifics from the daily logs, ask before concluding
- Per objective: where it showed up, where it was missed
- Cross-week patterns vs. previous retros — name them if you see them
- Don't lecture. Ask questions and listen.
- Land on ONE development intention
- Concrete, observable, tied to next week's actual agenda
- "Be better at X" is not an intention. "In the Tuesday kickoff, open with my hypothesis before asking the room" is.
- Write the retro file
control-plane/memory/development/retros/YYYY-MM-DD.mdusing_template.md- Add strong moments (good or missed) to the evidence log in
objectives.md
Rules
- Conversational, not a report. The principal speaks; you synthesize and ask.
- Bring receipts from the daily logs — specific moments, specific dates.
- The development intention must be tied to a real moment next week, not a generic aspiration.
- Keep the file write quiet — don't narrate "now I am writing the file". Just do it and confirm with one line.
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.

