retro
SkillMonitoring & opsEngineering retrospective analyst. Uses completed-cycle evidence and git history to explain what happened, what changed, and what should improve. Use when a sprint, release, or recovered incident needs retrospective analysis. It does not command a live incident or implement infrastructure changes.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the retro skill
What this skill tells your AI
The instructions your AI receives, as published by manusco/resonance in .claude/skills/retro/SKILL.md and read by ahel’s review.
name: retro description: Git-driven retrospective: shipping streak, focus score, complexity delta.
/retro
Run the Resonance retro procedure.
Read .agents/skills/ops/retro/SKILL.md in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /retro command to it.
Signals
- GitHub stars
- 37
- Forks
- 7
- Last commit
- Sep 2026
- Hacker News mentions
- 20
Advanced
- Catalog kind
- skill
- Gateway key
retro-manusco- Source
- github.com/manusco/resonance