retro

Generate falsifiable hypotheses from session signals and rank them by evidence.

28|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/mifunedev/openharness --skill retro-mifunedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/mifunedev/openharness/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/mifunedev/openharness --skill retro-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams and agents turn ongoing conversation signals into testable hypotheses, capture evidence, and decide what should be promoted into durable memory or identity constraints.

Core Features & Use Cases

  • Turn signals into falsifiable hypotheses with supporting and refuting evidence.
  • Score verdicts and confidence, then promote only durable insights into the harness memory tiers (memory/MEMORY.md, context/IDENTITY.md).
  • Use case: after a decision-heavy session, summarize lessons and gates for future sessions.

Quick Start

Invoke /retro to perform a session reflection and memory gating pass.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is evidence-based session reflection for AI memory management?

Evidence-based session reflection analyzes active conversation signals to generate falsifiable hypotheses, scoring them by supporting and refuting evidence before promoting durable insights into memory files.

How do I convert conversation signals into testable hypotheses for memory gating?

You convert conversation signals into testable hypotheses by applying a six-subsystem lens to the active session, ranking generated hypotheses by evidence, and promoting only well-supported insights to durable memory.

Does session reflection require any specific files or frontmatter to run?

Session reflection requires a SKILL.md frontmatter containing name and description fields, and writes promoted memory gating results directly to memory/MEMORY.md and context/IDENTITY.md files.

How do I trigger a session reflection and memory gating pass?

You trigger a session reflection and memory gating pass by invoking the /retro command, which analyzes the current conversation and writes well-supported hypotheses to memory and identity files.

What is the best way to decide which session insights should be promoted to durable memory?

The best way to decide which insights promote to durable memory is scoring falsifiable hypotheses by supporting and refuting evidence, then gating only medium-or-higher confidence results into memory files.

When should I not use automated memory gating for conversation analysis?

You should not use automated memory gating when your session lacks decision-heavy signals or testable outcomes, as the reflection process requires sufficient evidence to generate and rank falsifiable hypotheses.