retro

Analyze completed development cycles and incidents to extract lessons and action items.

8|Updated May 18, 2026
One-click install
npx skills add https://github.com/lalulali/vespyr --skill retro-lalulali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/retro
Command: npx skills add https://github.com/lalulali/vespyr --skill retro-lalulali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams learn from completed development cycles, incidents, and launches so they can improve estimates, processes, product quality, and shared knowledge instead of repeating the same mistakes.

Core Features & Use Cases

  • Cycle Review: Collect quantitative and qualitative evidence from delivery, QA, launches, and incident follow-up.
  • Cross-Functional Analysis: Review execution, process, product, and architecture from multiple agent perspectives.
  • Actionable Improvements: Synthesize findings into owned action items, memory updates, and traceable outputs for the next iteration.
  • Use Case: After a release or incident, use this Skill to produce a blameless retrospective that updates team memory and feeds improvements into the next planning cycle.

Quick Start

Use the retro skill to review the last release cycle, summarize what changed, and produce actionable improvements for the next iteration.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I conduct a blameless retrospective after a development cycle or incident?

A blameless retrospective analyzes completed development cycles and incidents through structured evidence gathering and multi-role review. It extracts lessons without assigning blame, producing owned action items and memory updates to improve the next iteration.

What's the best way to extract actionable improvements from a product launch review?

Extracting actionable improvements from a launch review involves collecting quantitative and qualitative evidence from delivery and QA. Cross-functional analysis synthesizes these findings into owned action items that feed directly into your next planning cycle.

How does cross-functional analysis work during a cycle review?

Cross-functional analysis during a cycle review examines execution, process, product, and architecture from multiple agent perspectives. This multi-role approach ensures comprehensive evaluation of the development cycle to calibrate processes and validate product quality.

Can I use incident analysis to update team memory and prevent recurring issues?

Incident analysis can update team memory by extracting lessons from post-incident reviews. It synthesizes findings into memory updates and traceable action-item outputs, preventing the team from repeating the same process or architecture mistakes.

What evidence is needed for process calibration and architecture follow-up?

Process calibration and architecture follow-up require structured evidence gathering from delivery, QA, launches, and incident follow-up. Both quantitative metrics and qualitative findings are necessary to produce accurate improvement actions for the next development cycle.