retro

Create timestamped RETRO.md entries with reflection sections and prior retro preservation.

2|1|Updated Feb 8, 2021
One-click install
npx skills add https://github.com/jstoobz/dotfiles --skill retro-jstoobz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/jstoobz/dotfiles/tree/main/claude/skills/session-kit/retro
Command: npx skills add https://github.com/jstoobz/dotfiles --skill retro-jstoobz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate a structured, honest retrospective document (RETRO.md) after a session, consolidating learning and actionable improvements.

Core Features & Use Cases

  • Automatic top-entry creation: Adds a new, timestamped retro at the top of RETRO.md and preserves previous retros under a dedicated section.
  • Guided reflection: Guides evaluation across Time well spent, Time wasted, Approach effectiveness, Tool/Skill usage, and Communication.
  • Recurring pattern detection: Flags recurring themes across multiple retros to highlight systemic issues.

Quick Start

Use the retro skill in the current working directory to create or update RETRO.md. If RETRO.md already exists, a new top entry is created with a timestamp and previous entries are preserved under "## Previous Retros".

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate retrospective documentation for team sessions?

You can automate retrospective documentation by generating a RETRO.md file with timestamped entries that capture what went well, what took longer than expected, and recurring patterns. This preserves prior retros under a dedicated section for continuous team reflection.

What sections should a session retrospective include for process improvement?

A session retrospective should include sections for What Went Well, What Took Longer Than Expected, What I'd Do Differently, Tool & Skill Notes, and Recurring Patterns. This structure guides evaluation of time spent, approach effectiveness, and communication to drive process improvement.

Can I preserve previous retros when adding a new entry to RETRO.md?

Yes, you can preserve previous retros when adding a new entry to RETRO.md. A new timestamped top section is created for the current session, while existing entries are automatically moved and preserved under a dedicated Previous Retros section.

How does recurring pattern detection work in team reflection documents?

Recurring pattern detection in team reflection documents flags recurring themes across multiple retros to highlight systemic issues. By reviewing successive timestamped entries in RETRO.md, you can identify recurring patterns in tool usage, communication, and process effectiveness.

Do I need any specific dependencies to generate markdown retrospectives?

No specific dependencies are required to generate markdown retrospectives. The process reads and updates a RETRO.md file directly in the current working directory, requiring no external components or frameworks to capture session reflections and preserve prior entries.