session-retrospective

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.