retro

Extract learnings and decisions from completed sessions into structured memory entries.

31|3|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/JeremyDev87/codingbuddy --skill retro-jeremydev87
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/JeremyDev87/codingbuddy/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/JeremyDev87/codingbuddy --skill retro-jeremydev87

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you capture durable learnings after complex sessions to prevent context fade and ensure concrete actions are documented for future improvements.

Core Features & Use Cases

  • Gather session context and extract keeps, problems, and evidence to justify decisions.
  • Classify learnings into memory, automation, or none and generate actionable outputs.
  • Produce structured memory entries and optional automation tasks or GitHub issues to track improvements.

Quick Start

Run the retrospective workflow immediately after a session to begin collecting context, documenting learnings, and creating memory entries.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I extract durable learnings from a completed coding session?

To extract durable learnings from a completed session, run a retrospective workflow to analyze context, identify keeps and problems, and generate structured memory entries. This prevents context fade and documents concrete actions for future improvements.

What is the best way to document action items after parallel work or multi-step plans?

Documenting action items after multi-step plans involves analyzing the session to classify learnings into memory or automation categories. This process generates formal outputs including memory entries, potential automation tasks, and optional GitHub issues with structured guardrails.

How do I generate memory entries and GitHub issues from session analysis?

Generating memory entries and GitHub issues from session analysis requires gathering session context to justify decisions. The workflow extracts evidence, classifies learnings, and enforces formal outputs to track improvements directly in your development environment.

When do I need to run a retrospective workflow for session analysis?

You need to run a retrospective workflow for session analysis immediately after completing complex sessions or parallel work. It captures evidence to justify decisions and classifies learnings before context fade occurs, ensuring durable improvements are documented.

Can I use session-analysis to classify learnings into automation tasks without dependencies?

Yes, you can use session-analysis to classify learnings into automation tasks without external dependencies. The workflow applies guardrails and a structured format to independently generate memory entries and suggest durable improvements from gathered session context.