session-retro

Analyze session mistakes and trace root causes into process improvements.

127|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/hanamizuki/solopreneur --skill session-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-retro
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/solopreneur/skills/session-retro
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill session-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Session retro identifies and analyzes mistakes in a conversation to produce durable process improvements, tracing root causes and surfacing actionable fixes.

Core Features & Use Cases

  • Structured review: scans the current session for correction signals and deviations.
  • Root-cause attribution: classifies issues by source (skill, CLAUDE.md, memory, or tool behavior).
  • Actionable reporting: generates a concise improvement plan and optional memory notes.
  • Safe memory saving: optionally saves key learnings for future sessions.

Quick Start

Start a retro after a session by asking for a concise report on what happened, why it happened, and what to improve next time.

Frequently Asked Questions about session-retro

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

FAQPage Schema
What is root-cause analysis for conversation errors and how does it work?▼

Root-cause analysis in a session retro classifies errors by source—skill behavior, configuration files, memory, or tool execution. It traces these deviations back to their origin to propose specific corrective actions.

How do I save retrospective learnings to memory for future sessions?▼

Yes, session retro can apply during active conversations or immediately after corrections occur. You simply request a concise report on what happened, why it happened, and what to improve next time.

Does a session review work without external dependencies or components?▼

The session retro workflow scans for deviations, analyzes findings, and presents a concise improvement report. It includes a decision step for optionally saving key learnings as memory notes for future reference.

Are there limitations to using an automated retrospective for process improvement?▼

Session retro relies on detecting correction signals within the conversation text, meaning it cannot analyze issues that lack explicit verbal or textual deviations. It requires a completed or active session log to function.