retrospective

Generates a structured Markdown retrospective document with actionable improvement suggestions after research tasks.

Updated Jan 22, 2026

Search Tags:#automation #workflow #documentation #research #retrospective #lessons learned

Ready to run

npx skills add https://github.com/tomlupo/ai-playground --skill retrospective-tomlupo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/tomlupo/ai-playground/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/tomlupo/ai-playground --skill retrospective-tomlupo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a structured retrospective document at the end of research sessions, capturing what went well, what went poorly, what was ugly, and actionable improvement ideas to inform future work.

Core Features & Use Cases

Phase-based analysis: Guides context gathering, self-reflection, skills utilization, and document generation to produce a consistent report.
Executive summary & insights: Produces a concise overview with measurable improvement ideas and final recommendations.
Reusable templates: Provides a repeatable format suitable for post-mortems on research tasks and feature work.

Quick Start

Generate a retrospective for the current research session and review or edit the generated Markdown to fit your branch and task naming conventions.

Frequently Asked Questions about retrospective

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

FAQPage Schema

What is a structured research retrospective and when do I need one?▼

A structured research retrospective analyzes what went well, what went badly, and what was ugly in a session. You need one after completing research tasks and before final commits on feature branches to capture actionable improvements.

How do I automate post-mortem documentation for feature work?▼

You automate post-mortem documentation by using a phase-based workflow that gathers context, performs self-reflection, analyzes skills utilization, and generates a Markdown document with an executive summary and actionable insights.

What's the best way to capture lessons learned from a development session?▼

The best way to capture lessons learned is to generate a structured retrospective document that reviews progress and outputs actionable improvement ideas to inform future work. This provides a repeatable format suitable for feature work.

Does this retrospective workflow support standard Markdown export?▼

Yes, the retrospective workflow supports Markdown export. It generates a structured retrospective document in Markdown format, which you can review or edit to fit your branch and task naming conventions.

Can I use this for post-research analysis on feature branches?▼

Yes, you can use this for post-research analysis on feature branches. It applies after completing research tasks and before final commits to capture what went well, what went poorly, and actionable insights.

What phases does the automated retrospective workflow include?▼

The automated retrospective workflow includes four phases: context gathering, self-reflection, skills analysis, and document generation. These phases produce a consistent report with measurable improvement ideas.