Verified:GitHub

session-retrospective

Distill Claude Code session transcripts into evidence-backed retrospective reports.

18|9|Updated Apr 8, 2026

Search Tags:#retrospective #evidence-based #workflow documentation #session mining #team memory #ack-gated updates #Claude Code transcripts

Ready to run

npx skills add https://github.com/arozumenko/sdlc-skills --skill session-retrospective-arozumenko

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-retrospective
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/session-retrospective
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill session-retrospective-arozumenko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It turns scattered Claude Code transcripts and sub-agent activity into evidenced, approval-gated improvements for team memory and shared workflow docs.

Core Features & Use Cases

Session distillation to a bounded digest: Summarizes transcripts into a compact markdown report (never raw JSONL) that highlights tool errors, retry/loop behavior, file churn, and candidate corrections with session-id evidence.
Evidence-driven mapping to write targets: Routes role-specific lessons to the appropriate memory areas, routes team-wide process changes to .agents/workflow.md and .agents/conventions.md, and records every run to a dated retrospectives report.
Anti-memory-poisoning guardrails: Read-only parsing, propose-then-wait for user ack, and watermark advancement only after successful writes.

Quick Start

Ask scout to run the session retrospective digest for your project, then review the proposed diffs and approve the write.

Frequently Asked Questions about session-retrospective

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

FAQPage Schema

How do I generate a retrospective from Claude Code session transcripts?▼

To generate a retrospective from Claude Code session transcripts, the Skill parses read-only JSONL transcripts and distills them into a bounded markdown digest highlighting tool errors, retry loops, and file churn with session-id citations.

What is session mining for team memory and how does it work?▼

Session mining for team memory extracts evidence-backed lessons from past coding sessions, mapping role-specific insights to memory areas and routing process changes to shared workflow documentation like conventions files.

How do I diagnose workflow slowdowns using past session evidence?▼

You diagnose workflow slowdowns by mining session transcripts to identify retry behaviors, tool errors, and file churn, then mapping those evidence-backed findings to candidate corrections in shared workflow docs.

Can I update workflow documentation automatically from Claude Code transcripts?▼

You can update workflow documentation from Claude Code transcripts through an approval-gated process where the Skill proposes diffs to conventions files and advances a watermark only after you acknowledge successful writes.

What guardrails prevent memory poisoning when running session retrospectives?▼

Anti-memory-poisoning guardrails include read-only transcript parsing, a propose-then-wait mechanism requiring user acknowledgment before writes, and watermark advancement that occurs only after successful write operations.

Does the session retrospective require any specific dependencies or setup?▼

The session retrospective requires no external dependencies, needing only access to Claude Code session transcripts to parse and distill into an evidence-backed markdown report for team review.