session-retrospective

Capture and categorize development session learnings across seven perspectives.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/RyoMa99/dotfiles --skill session-retrospective-ryoma99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-retrospective
Source: https://github.com/RyoMa99/dotfiles/tree/main/dot_claude/skills/session-retrospective
Command: npx skills add https://github.com/RyoMa99/dotfiles --skill session-retrospective-ryoma99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structuredly captures learnings at the end of a development session to prevent knowledge loss, surface automation opportunities, and route insights to the correct storage locations so team knowledge is discoverable and actionable.

Core Features & Use Cases

  • Seven-perspective extraction: Systematically identifies domain knowledge, technical learnings, automation opportunities, knowledge updates, project CLAUDE.md gaps, plan calibration validity, and design debt.
  • Guided review flow: Walks the user through session scanning, presents a templated report, requests approval, and only then performs saving actions.
  • Destination mapping and actions: Uses reference rules to map findings to specific files or locations (rules, skills, hooks, CLAUDE.md, GitHub Issues) and can create issues for significant design debt after user confirmation.
  • Use case: At the end of a coding session, extract key learnings, propose where each insight should be saved, and create an issue for any refactor-worthy design debt after approval.

Quick Start

At the end of your development session, run the session-retrospective to extract learnings across seven perspectives, review the proposed mappings, and approve which items to save.

Frequently Asked Questions about session-retrospective

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

FAQPage Schema
How do I capture development session learnings to prevent knowledge loss?

Development session learnings are captured by systematically scanning the session across seven perspectives, including domain knowledge, technical learnings, and design debt, then routing them to configured destinations after explicit user approval.

What is the best way to run an end-of-session retrospective for coding projects?

An end-of-session retrospective extracts key learnings through a guided review flow, presents a templated report mapping insights to specific files, and only saves items after user approval to ensure team knowledge remains actionable.

How do I track design debt discovered during a coding session?

Design debt is tracked by identifying it during session scanning and optionally creating GitHub issues for significant refactor-worthy items, but only after receiving explicit user confirmation to persist the findings.

Can I map session insights to specific files like CLAUDE.md automatically?

Session insights are mapped to specific files like CLAUDE.md, rules, skills, and hooks using reference rules, ensuring findings are routed to the correct storage locations for discoverability.

Does the retrospective process require manual approval before saving knowledge updates?

The retrospective process requires explicit user approval before persisting any items, walking you through session scanning and presenting a templated report before performing any saving actions.

What perspectives should a session retrospective cover to surface automation opportunities?

A session retrospective covers seven perspectives: domain knowledge, technical learnings, automation opportunities, knowledge updates, project CLAUDE.md gaps, plan calibration validity, and design debt.