retro

Name: retro
Availability: InStock
Author: Steven

Analyze development conversations to generate friction logs and improvement proposals.

Updated Apr 7, 2026

Search Tags:#automation #workflow #development #retrospective #memory #friction

Ready to run

npx skills add https://github.com/stevenmunoz/turbo-ai-exercise --skill retro-stevenmunoz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/stevenmunoz/turbo-ai-exercise/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/stevenmunoz/turbo-ai-exercise --skill retro-stevenmunoz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Session retrospectives identify friction, repetition, and optimization opportunities across development sessions. This skill analyzes conversations to surface bottlenecks, repeated questions, and missed automation, then outputs actionable improvements such as patches to CLAUDE.md, memory updates, and new skill proposals.

Core Features & Use Cases

Analyze conversations to extract friction points and patterns (back-and-forth debugging, repetitive questions).
Compile and update a persistent friction log (references/friction-log.md) for cross-session learning.
Propose CLAUDE.md patches, memory updates, and new skill ideas to improve workflows.
Generate structured retrospectives that guide future sessions and automation.

Quick Start

Run the retro workflow after finishing a session to generate a structured session retro report.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I identify friction and bottlenecks in my development sessions?▼

Session retrospectives identify friction by analyzing development conversations to surface repeated questions, back-and-forth debugging, and automation gaps. This process extracts friction patterns and compiles a persistent friction log for cross-session learning.

What is the best way to automate session retrospectives for software engineering?▼

Automated session retrospectives analyze ongoing code reviews and team discussions to generate structured reports. This surfaces optimization opportunities and outputs actionable improvements like CLAUDE.md patches and memory updates to guide future sessions.

Can I use conversation analysis to propose new workflow automation?▼

Conversation analysis extracts automation gaps and recurrent questions from development sessions to propose new skill ideas. It generates targeted proposals and memory updates to optimize workflows and reduce future friction.

How do I create a persistent friction log for cross-session development learning?▼

A persistent friction log compiles extracted friction points and patterns from development conversations into a structured file. Updating this log across sessions captures bottlenecks and repetitive questions to improve future automation.

Does session retrospective analysis require any specific dependencies or components?▼

Session retrospective analysis requires no external dependencies or components to function. It independently processes development conversations to generate friction logs, CLAUDE.md patches, and skill proposals.

When should I run a development session retrospective?▼

Run a development session retrospective after finishing a session to analyze conversations for friction and repetition. This timing captures immediate bottlenecks and missed automation opportunities to generate actionable workflow improvements.