retro

Extract durable, codifiable learnings from iterations with quality-gated triage.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/eumemic/dev-skills --skill retro-eumemic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/eumemic/dev-skills/tree/main/skills/retro
Command: npx skills add https://github.com/eumemic/dev-skills --skill retro-eumemic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The retro skill prevents wasted cycles by turning experience from an iteration, full session, or pause point into durable, codifiable learnings—while avoiding noisy or one-off changes that would bias future agent behavior.

Core Features & Use Cases

  • Quality-gated retros: Identifies only recurring, codifiable, and high-leverage findings, and explicitly produces no actionable output when nothing clears the bar.
  • Scoped analysis modes: Supports --scope=iteration (loop-driver iteration), --scope=session (full conversation), and --scope=pause (self-invoked when waiting on async work).
  • Action classification & execution: Selects an action item type (memory entries, skill edits, scripts, constellation issues) and routes autonomous versus approval-needed items via clear autonomy zones.

Quick Start

Use retro to reflect on this iteration by running: /retro --scope=iteration

Frequently Asked Questions about retro

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

FAQPage Schema
How do I extract durable learnings from an agent workflow session?

To extract durable learnings from a workflow session, run a retrospective with scoped event analysis to identify recurring, codifiable findings. This process reviews artifacts and classifies high-leverage insights into autonomous memory updates or approval-needed skill edits.

What is a quality gate in a dev-infrastructure retrospective?

A quality gate in a retrospective filters out noisy, one-off changes to prevent biased future agent behavior. It ensures only recurring, codifiable, and high-leverage findings clear the bar to produce durable workflow improvements.

How do I run a retrospective after a loop-driver iteration?

Run a retrospective after a loop-driver iteration by executing the command with the iteration scope. This triggers candidate-finding triage to evaluate events, applying recurring and codifiable checks to surface actionable dev-infrastructure learnings.

Can I trigger a retrospective automatically when an agent pauses for async work?

Yes, you can trigger a retrospective automatically when an agent pauses for async work by using the pause scope. This self-invoked analysis evaluates the waiting period to find codifiable workflow improvements without manual intervention.

How are action items classified during a workflow retrospective?

Action items during a workflow retrospective are classified by routing them into autonomous execution or approval-needed surface actions. Selected types include memory entries, skill edits, scripts, and constellation issues, governed by clear autonomy zones.