When should I run the Retro skill?

Run it after completing a major feature or mid-session if the collaboration feels 'rocky' or inefficient to identify process improvements.

Will it automatically change my files?

No, all process improvements are presented as proposals. Claude only implements changes to your skills or documentation after receiving your explicit approval.

How does it find friction points?

It analyzes the current conversation context and can launch a subagent to grep through recent session history for signals like user corrections, interruptions, or tool failures.

What is the difference between a Lite and Full retro?

A Full retro incorporates deep user feedback and pauses for alignment, while a Lite retro is a quick scan that only proposes changes if significant issues surface.

Process Retrospective

Name: Process Retrospective
Author: suzbot

bysuzbot

•

Productividad y Flujo de Trabajo

Optimizes AI-human collaboration by identifying and resolving workflow friction through post-feature reflection and history analysis.

The Retro skill provides a structured framework for Claude to analyze recent development sessions and identify recurring friction points. By evaluating interrupted actions, requested clarifications, and context slips, the skill proposes high-leverage refinements to project documentation, custom skills, and communication norms. It features an autonomous history search capability to find patterns across multiple sessions, ensuring that process improvements are based on actual evidence rather than speculation, ultimately reducing future cognitive overhead and token usage.