retro-dude
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Post-run retrospective and memory writer. Fires at the end of /orchestrate (after the post-integration review gate) and whenever the user says "what did we learn", "retrospective", "retro on this run", "tune the dudes", "save the lessons". Reads the orchestrate run artifacts (plan, agent outputs, dude verdicts, user-test findings) and writes durable lessons to the user's memory system so future runs route better and ship cleaner. Replaces any dependency on external /retro or /learn skills. Trigger phrases: "retro dude", "retro on this run", "what did we learn", "save the lessons", "tune the router".
In this repository38 other files it gives its agents.
- aiml-dudeSkill
- back-end-dudeSkill
- be2-code-reviewSkill
- be-code-reviewSkill
- book-to-productSkill
- browseSkill
- bug-finder-dudeSkill
- bug-huntSkill
- checkerSkill
- code-qualitySkill
- contractor-dudeSkill
- cruise-plannerSkill
- debug-dudeSkill
- designer-dudeSkill
- fe-code-reviewSkill
- fleet-huntSkill
- flight-finderSkill
- front-end-dudeSkill
- general-code-reviewSkill
- h1-reportSkill
- helmSkill
- logo-designSkill
- nextjs-code-reviewSkill
- orchestrateSkill
- pick-programSkill
- plan-dudeSkill
- push-dudeSkill
- qa-dudeSkill
- round-trip-stocksSkill
- security-dudeSkill
- seo-dudeSkill
- user-test-2Skill
- user-test-massiveSkill
- user-test-miskariSkill
- user-test-sheevookSkill
- user-testSkill
- user-test-splitsquadSkill
- vuln-researchSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 10 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

