Menu

Individual skill

retro

Review a session or a whole workloop run for recurring pitfalls and wasted effort. Output evidence-backed findings and suggested improvements for the user to decide; use when asked for retro or when assessing a completed run before archival.

skills/retro/SKILL.md

Read pinned source

Source commit ed8aa57b1aca020e35f1eb85838bd2b21f56d266

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
11
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Retro

Find experience worth carrying into the next run. Output findings and suggestions; implementing them is a separate user decision. Save the retrospective when working on a run, but leave project files, rules, hooks and backlogs unchanged.

Read [writing-for-agents](../writing-for-agents/SKILL.md) when phrasing guidance for future agents. The [upstream retro](reference/upstream.md) is optional background for investigating a finding. Its advice to build checks is a possible recommendation here, not authorization to implement one.

## What to look for

Use these lenses rather than a mandatory checklist or score:

- **Recurring third-party failures:** dependencies, external APIs, tools or environments that keep failing. Look for confirmed limits and useful recovery methods.
- **Business pitfalls:** domain meanings, state transitions or edge cases repeatedly misunderstood.
- **Repeated wrong behavior:** losing context, recreating worktrees unnecessarily, duplicate dispatch or claiming completion before verification.
- **Repeated exploration:** rediscovering the same entry point, retrying ineffective approaches or repeating work whose answer was already available.