retro
SolidScientific session-closing retrospective: scan the current conversation, turn each signal into a falsifiable hypothesis, cite session evidence for AND against it, assign a verdict (supported / refuted / inconclusive) and a confidence level, then promote only supported, sufficiently-confident hypotheses into the harness memory tiers (.oh/memory/MEMORY.md, .oh/context/IDENTITY.md) behind a propose-then-confirm gate. Reflects on six learning/knowledge subsystems through the lens of this session — continual learning, context compression, reinforcement learning, wiki, docs, and memory scaffolding — and points at the deep-dive lint/audit skills rather than running them. Operationalizes the Memory Improvement Protocol (.oh/skills/retro/references/memory-protocol.md) as an explicit, evidence-driven, session-closing skill rather than a per-run afterthought. Always appends a log entry. TRIGGER when: /retro invoked, or session closing with decisions, surprises, or failures worth preserving.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- mifunedev
- Repository
- mifunedev/openharness
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
retro
Use when a Claude Code session ends or is declared finished, a friction needs fixing, a reusable learning needs capturing, local memory needs promoting upward, or for cross-session audits — detect friction AND learnings, route each to the right destination, and gate 'done'. Triggers: /retro, /retro done, 'retrospective', 'capture this learning', 'fix this skill', 'promote memory', 'audit', 'alles erledigt'.
retro
Use when a session should become durable improvements (CLAUDE.md rules, hooks, memory, skills) — the user asks ('/retro', 'retrospective', 'postmortem', 'what went wrong', 'find friction', 'capture lessons', 'lessons learned', 'run a retro'), OR a session is wrapping up after notable friction (repeated failures, rework, multiple corrections) with no retro yet. Offer it proactively at session end; retro only proposes and never writes without approval, so offering is safe.
retro
Harvest a finished milestone or painful session into durable harness improvements — corrections, surprises, and re-derived knowledge become candidate skill edits, hooks, adapter fields, or memory/instruction lines, each behind the normal sign-off gate. Use after a milestone, after repeated failed attempts, or on "retro" / "make sure this doesn't happen again".