retro

Name: retro
Availability: InStock
Author: seth090502

Capture session outcomes into structured Markdown files with Git commits.

Updated Jun 13, 2026

Search Tags:#decision logging #knowledge retention #session capture #session review #structured documentation

Ready to run

npx skills add https://github.com/Seth090502/osanwe-public --skill retro-seth090502

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Seth090502/osanwe-public/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/Seth090502/osanwe-public --skill retro-seth090502

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill captures and preserves the outcomes of a session in a structured format, ensuring that decisions, learnings, and follow-ups are not forgotten or lost.

Core Features & Use Cases

Atomic Session Capture: Captures decisions, learnings, follow-ups, and insights from a session in a single atomic commit.
Multi-File Persistence: Persists captured information to multiple files (sessions-log, decision-log, daily note, hot.md) for comprehensive tracking.
Use Case: After a productive work session, use this Skill to automatically document decisions made, new learnings, actionable follow-ups, and insights gained.

Quick Start

Use the /retro command to capture the current session's outcomes.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I capture decisions and learnings from a work session for future reference?▼

To capture decisions and learnings for knowledge retention, this Skill structures session outcomes into a single atomic commit. It automatically persists data across multiple files like sessions-log and decision-log.

What is the best way to log follow-ups and insights in Markdown?▼

The best way to log follow-ups and insights in Markdown is through structured documentation that writes to multiple files like daily notes and hot.md. This ensures comprehensive tracking of actionable items alongside session learnings.

Do I need Git to use this session capture and review process?▼

Yes, Git is required for this session capture process because it handles version control. It utilizes Git to commit the structured outcomes of your session atomically alongside Markdown documentation.

Can I use Python to automate session review and structured documentation?▼

Yes, Python is utilized for processing and analysis in this session review and structured documentation workflow. It processes captured session data to extract decisions, learnings, and follow-ups.

How does atomic session capture improve knowledge retention?▼

Atomic session capture improves knowledge retention by preserving decisions, learnings, and follow-ups in a structured format within a single commit. This prevents session outcomes from being forgotten or lost over time.

What files are updated when I log a session for decision logging?▼

When logging a session for decision logging, multiple files are updated including sessions-log, decision-log, daily note, and hot.md. This multi-file persistence ensures comprehensive tracking of all captured outcomes.