retrospect

Scan lab-notebook, journal, ideas, git log, and TODO.md files to generate retrospective reports.

18|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/safety-quotient-lab/psychology-agent --skill retrospect-safety-quotient-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospect
Source: https://github.com/safety-quotient-lab/psychology-agent/tree/main/.claude/skills/retrospect
Command: npx skills add https://github.com/safety-quotient-lab/psychology-agent --skill retrospect-safety-quotient-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill systematically reviews accumulated work across multiple sessions to identify patterns, predictions, wins, recurrences, and carryover items that might be missed in individual session reviews.

Core Features & Use Cases

  • Pattern Identification: Analyzes past work to find recurring themes, successful strategies, and unfulfilled predictions.
  • Win Discovery: Surfaces accomplishments that may not have been formally documented as lessons.
  • Carryover Analysis: Tracks persistent tasks or issues that are repeatedly deferred.
  • Use Case: After completing a project phase, use this Skill to generate a comprehensive retrospective report highlighting key learnings, successful approaches, and areas for improvement based on the entire project history.

Quick Start

Run a full retrospective scan to analyze all accumulated work for patterns.

Frequently Asked Questions about retrospect

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

FAQPage Schema
How do I generate a project retrospective from git logs and TODO files?

To generate a project retrospective, the Skill scans accumulated lab-notebooks, journals, ideas, git logs, and TODO.md files. It analyzes this historical data to identify emergent themes, carryover patterns, and lessons learned across multiple sessions.

What is retrospective pattern analysis and how does it uncover hidden work patterns?

Retrospective pattern analysis systematically reviews past work sessions to find recurring themes, successful strategies, and unfulfilled predictions. It surfaces hidden patterns by cross-referencing historical documentation to highlight wins and persistent carryover items.

Can I track deferred tasks and carryover items across multiple project sessions?

Yes, you can track deferred tasks through carryover analysis. The Skill scans your historical work data to identify persistent issues or tasks that are repeatedly deferred, documenting them in a comprehensive retrospective report.

When do I need to run a retrospective scan on my project documentation?

You need to run a retrospective scan after completing a project phase or when you need to document lessons learned. It helps identify emergent themes and unfulfilled predictions by analyzing your entire project history comprehensively.

Does this retrospective analysis tool require specific file formats to work?

The retrospective analysis requires specific file types to function properly. It analyzes lab-notebook, journal, ideas, git log, and TODO.md files to scan accumulated work and generate comprehensive reports for administrative and research workflows.