retrospective

User friction signals and correction moments are captured silently during a Claude Code session by noting corrections, redo requests, and repeated back-and-forth interactions to identify areas for improvement.

Run a retrospective by scanning the whole conversation to classify each friction moment, prioritizing up to five findings, and routing them to appropriate context files like rules, preferences, or workflows.

The retrospective skill routes findings safely by verifying proposals, avoiding duplicates and contradictions, preventing oversized files, writing confirmed entries to the correct context files, and updating the session journal.

Automating session improvement without manual bookkeeping is achieved by capturing real-time friction signals, classifying them during a retrospective, and automatically writing the insights to project memory and rules files.

No dependencies are required to run the retrospective skill. It operates independently to scan conversations, classify friction signals, and update context files within the development environment.

You should avoid relying solely on an automated retrospective when context files are already oversized or prone to contradictions, as the skill prioritizes safety checks to prevent duplicate or conflicting entries.